Re: [Beaver-devel] Happy 2009

[Higor Eurípedes]

> 1) can you please remove the api library. it's never needed and thus
> useless. in the end everything get's compiled it anyway so why don't do
> it in the first place?

You mean libbeaverapi.a ? hmm i could do it, but it would break in some automake
versions in the compile process inside a subdirectory like src/api.
library compiling replacements?

1 - move src/api one level up example: beaver0.4.0/api instead of
beaver0.4.0/src/api
2 - ignore the most ppl (most ppl has autoconf 2.13 instead of 2.50+,
even up to date systems.
     I had 2.13 and 2.63 in my PC. 2.63 has no problem compiling
src/api directly, but my friend
     had 2.61 and got problems, automake shows warnings and generate
bad configure scripts and/or Makefiles)

> 2) the "api.h" isn't needed by the user and doesn't need any copying. it
> can be removed from the install process

Ok, i will remove it.

> 3) is it possible to add the nice output also to plugin compilation?

I will work on it.

> 4) I would say we settle on "-fPIC -O2" as CFLAGS. I don't think that
> the normal user want to have all the debug flags included etc... Also if
> you use -g then -O2 has no effect. It would be also cool, that the
> installed binary could be 'strip'ped.

Does compiling with -g change anything on user's experience?
About -g + -O2: OOps, my fault
.
> It would be also cool, that the installed binary could be 'strip'ped.

Sure.

Bye

-- 
Higor Euripedes (enygmata)