We do things a little differently to this in the
Makefile.ams.
If someone passes in CCFLAGS (or defines a CCFLAGS)
environment variable, then this is used verbatim. The
user is then responsible for all CCFLAGS options
passed to the compiler.
We also use CPPFLAGS (IIRC) to enable the user to
specify some flags which are appended onto the
otherwise machine-generated CCFLAGS.
If the user wants to just specify optimization/debug
level, then I believe that he should pass
--enable-optimization='-03' to configure.
These look way too complicated! And are they well-docmented behaviors?
I think I will implement only what I proposed. At least I need to
write only one line in INSTALL.scons, not three paragraphs.
Perhaps you should invest some time in looking what
has gone before? You appear to have re-invented the
wheel several times already in this scons work...
I know. Part of the reason is that I am new to scons. For example, I
did a bunch of tests, and figured out later that they can be done with
a single scons call.
Another part of the 'reinvent-the-wheel' can not be avoided since I am
re-implementing a build system. Life became a bit difficult when
libraries like gettext only support autotools and I have to read
things like iconv.m4.
I would have thought it would become frustrating
eventually ;-)
Not yet. It is much more fun to program in python than m4, and I am
glad to see that scons can do more and more now, with actually fewer
lines of code.
Bo
