Re: Auto-tools & Win32 & Borland C++ Builder

[Ralf Corsepius <corsepiu at faw dot uni-ulm dot de>]

Tom Tromey wrote:
> 
> >>>>> "Rasmus" == Rasmus Tamstorf <tamstorf@fa.disney.com> writes:
> 
> Rasmus> I think the issue is that with autoconf you setup your
> Rasmus> compiler flags (debug / optimized etc) for the entire build
> Rasmus> tree when you run ./configure. However, while developing you
> Rasmus> may want 90% to be optimized and only the remaining 10% (a
> Rasmus> single or a few subpackages) which you are actively debugging
> Rasmus> to be build with debuginformation. At least that's an issue I
> Rasmus> have ;)
> 
> Oh.  I never even considered that as a problem.  I daily do things
> like this:
> 
>     cd gcc
>     make mostlyclean
>     make CFLAGS=-g
> 
> Then gcc is built with debugging but the rest of my tree remains
> untouched.  It is easy, even trivial, to write your package's
> configury so that this works.

I think, there are two issues realated to this approach, AFAIS
people are keen on to see:
* library-variants, like they were used to exist with Imake, i.e.
libfoo.a (optimized), libfoo_g.a (debug), libfoo_pg (profile,debug)
etc.
* hard-coded flags for certain toolchains and flag sets for such
build-variants.

In my understanding, both topics at present time are not subject to
auto*tools' objectives, but people seem to be thinking they are. [At
least the first of the two topics above have caused me major grief
in discussions with package's maintainers who insist on such
feature].

Ralf.