[Scons-users] scons and clang++

[Dirk Bächle]

On 18.07.2014 13:45, Florian Lindner wrote:
> Dirk Bächle wrote:
>
>> On 18.07.2014 11:23, Florian Lindner wrote:
>>> Dirk Bächle wrote:
>>>
>>>> [...]
>>> Isn't the point of calling env = conf.Finish() not to allow you to set
>>> all variables in env and test not before calling Finish()?
>> And what if your configure tests depend on an environment having been
>> setup properly? ;)
> So you recommend to import the entire os.environ always?
No, definitely not. I was just trying to point out why it could be 
important to setup the ENV variable right in the call of the Environment 
constructor. How much of the shell environment you pull into your build, 
is completely up to you...

>> The basic idea here is to setup your Environment first (PATH + detected
>> Tools), and then with Configure() to further refine your build
>> description by adding include and lib paths, based on what
>> libraries/packages you find (based on the Environment, as defined in
>> step 1).
> Right now I have blocks like:
>
> if env["feature"]:
>    env.AppendUnique(LIBPATH = [someAdditionalLibs])
>    if not conf.CheckHeader('header.h'):
>       failOrWarn()
>
> see http://pastebin.com/GrJ2SFTu
>
> Is that a problem like that?

No, I don't see a problem here.

Dirk