Re: Building two programs and setting INCLUDE for each (with :conf rule)

Bram Neijt wrote:

> Locally defining the variables now works, however, I now have a small
> problem with the (still experimental) :conf rule
> I would like to be able to use the :conf rule just like I use the
> :program rule now, adding variable only to the actual conf rule:
> 
> (Something like this, which doesn't work)
> :conf {var_INCLUDE =3D $MyOwnList } {required} gtkmm.h
> 
> However, reading the documentation on
> http://www.a-a-p.org/exec/user-configure.html it seems that I will be
> forced to overwrite the INCLUDE global variable before use and later
> set it back like this:
> 
> oldinclude = $INCLUDE
> INCLUDE = $MyOwnList
> :conf {required} gtkmm.h
> INCLUDE = $oldinclude
> 
> How should this be handled? (The above seems just silly)

This is indeed how you need to do it now.  The idea of ":conf" is that
$INCLUDE is set while configuring.  But you can make exceptions.

":conf" would set HAVE_GTKMM_H, but if you change $INCLUDE afterwards
that becomes invalid.  Thus it's a bit tricky.

I don't know what a "clean" solution would be without messing with the
normal way of configuring.  It would probably require having the defines
depend on the use $INCLUDE, but that quickly gets complicated.

-- 
How To Keep A Healthy Level Of Insanity:
11. Specify that your drive-through order is "to go".

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///        Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\     Buy LOTR 3 and help AIDS victims -- http://ICCF.nl/lotr.html   ///


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf