Ossama Othman <[EMAIL PROTECTED]> writes:
> Would it be worthwhile to add a "--enable-debug" and a
> "--enable-optimize=level" set of configure script options?
A problem with that is that it moves the responsability of keeping
track of which compilers accept which options from the user to the
macro. "-g -O2" is only the default when running with gcc. And I've
no clue as to what would be the appropriate flags when using
e.g. Visual C*. So I'm not sure it's worth the effort.
> Thinking about it now, I realize that this may break some existing
> configure scripts since they may already implement these options.
I don't feel this is a large problem.
> There was mention of the CVS autoconf handling this differently. What
> does it do?
You can put variables at the configure command line like:
configure CFLAGS=...
/assar
