<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Fri, 2010-12-03 at 13:58 -0500, Gaetan Nadon wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#737373">> + CC C compiler command</FONT></TT><BR>
<TT><FONT COLOR="#737373">> + CFLAGS C compiler flags</FONT></TT><BR>
<TT><FONT COLOR="#737373">> + LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a</FONT></TT><BR>
<TT><FONT COLOR="#737373">> + nonstandard directory <lib dir></FONT></TT><BR>
<TT><FONT COLOR="#737373">> + CPPFLAGS C/C++/Objective C preprocessor flags, e.g. -I<include dir> if</FONT></TT><BR>
<TT><FONT COLOR="#737373">> + you have headers in a nonstandard directory <include dir></FONT></TT><BR>
<TT><FONT COLOR="#737373">> + CPP C preprocessor</FONT></TT><BR>
<TT><FONT COLOR="#737373">> CONFFLAGS: additional flags to pass to all configure scripts</FONT></TT><BR>
<TT><FONT COLOR="#737373">> CONFCFLAGS: additional compile flags to pass to all configure scripts</FONT></TT><BR>
<TT><FONT COLOR="#737373">> MAKEFLAGS: additional flags to pass to all make invocations</FONT></TT><BR>
<BR>
<TT><FONT COLOR="#1a1a1a">If we're picking these up from the environment, then why do we need to</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">pass them to configure?</FONT></TT><BR>
</BLOCKQUOTE>
I struggled with this question as I noticed it in the current implementation.<BR>
<BR>
I vaguely recall Automake recommending specifying it on the command line, though they make every effort to ensure it works properly.<BR>
<BR>
</BLOCKQUOTE>
<BR>
This is where "I vaguely" recall seeing the recommendation. Right in ./configure --help:<BR>
<BR>
<BLOCKQUOTE>
<PRE>
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.
</PRE>
</BLOCKQUOTE>
:-)
</BODY>
</HTML>