[PATCH modular 2/3] build.sh: support CC, CPP, CPPFLAGS and CFLAGS

[Gaetan Nadon]

On Fri, 2010-12-03 at 13:58 -0500, Gaetan Nadon wrote:

> > > +  CC          C compiler command
> > > +  CFLAGS      C compiler flags
> > > +  LDFLAGS     linker flags, e.g. -L<lib dir> if you have
> > libraries in a
> > > +              nonstandard directory <lib dir>
> > > +  CPPFLAGS    C/C++/Objective C preprocessor flags, e.g.
> > -I<include dir> if
> > > +              you have headers in a nonstandard directory
> > <include dir>
> > > +  CPP         C preprocessor
> > >   CONFFLAGS:  additional flags to pass to all configure scripts
> > >   CONFCFLAGS: additional compile flags to pass to all configure
> > scripts
> > >   MAKEFLAGS:  additional flags to pass to all make invocations
> > 
> > If we're picking these up from the environment, then why do we need
> > to
> > pass them to configure?
> 
> I struggled with this question as I noticed it in the current
> implementation.
> 
> I vaguely recall Automake recommending specifying it on the command
> line, though they make every effort to ensure it works properly.
> 


This is where "I vaguely" recall seeing the recommendation. Right
in ./configure --help:


        Usage: ./configure [OPTION]... [VAR=VALUE]...
        
        To assign environment variables (e.g., CC, CFLAGS...), specify them as
        VAR=VALUE.  See below for descriptions of some of the useful variables.

:-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101204/1b1f959c/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101204/1b1f959c/attachment-0001.pgp>