[Scons-users] CPPDFINES oder conf.Define

[Florian Lindner]

Bill Deegan wrote:

> Florian,
> 
> Why do you do?
> conf = Configure(env)
> 
> This is not usually needed unless you are using SCons's configure
> capability which is similar to GNU AUTOCONF

I guess I do use it, having a lot of CheckLib and alike calls. Isn't that 
the usual way of using scons?

Rgds,
Florian


> 
> On Sat, Aug 16, 2014 at 5:45 AM, Florian Lindner <mailinglists at xgm.de>
> wrote:
> 
>> Gary Oberbrunner wrote:
>>
>> > On Fri, Aug 15, 2014 at 4:44 AM, Florian Lindner <mailinglists at xgm.de>
>> > wrote:
>> >
>> >> Hello,
>> >>
>> >> http://www.scons.org/doc/production/HTML/scons-user.html mentions
>> >> CPPDEFINES
>> >> for setting defines.
>> >>
>> >> http://www.scons.org/doc/production/HTML/scons-man.html on the other
>> hand
>> >> mentions sconf.Define(symbol, [value, comment]) for that.
>> >>
>> >> What is right way to set defines for C++?
>> >>
>> >
>> > CPPDEFINES is almost always the right answer.  sconf.Define() should
>> > only be used to add to the set of CPPDEFINES within a Configure
>> > context.
>>
>> What do you mean by 'within a configure context'. Usually I do
>>
>> env = Environment(variables = vars, ENV = os.environ)
>> conf = Configure(env)
>>
>> at the top of my SConstruct.
>>
>> So I am always inside a configure context, am I not?
>>
>> Rgds,
>> Florian
>>
>> _______________________________________________
>> Scons-users mailing list
>> Scons-users at scons.org
>> http://four.pairlist.net/mailman/listinfo/scons-users
>>