[Scons-users] What is the best approach with SConstruct calling SConscript

Bill Deegan bill at baddogconsulting.com
Tue Nov 8 12:48:57 EST 2016


Sounds like you want to change the variant dir from within the variant
dir....
Effectively

VariantDir('.','win32')


That's not going to work.

What's the benefit of setting the variant dir from within the SConscript?

-Bill


On Mon, Nov 7, 2016 at 1:59 PM, Pierre-Luc Boily <pierreluc.boily at gmail.com>
wrote:

> I have around 5 SConscript files (on a total of 160) that needs to compile
> on
> *both *win32 and win64 target.
>
> Let say that sconsScriptA needs to be built in both win32 and win64.  Does
> that mean, following your suggestion, that my SConstruct would need to do
> something like :
>
> |SConscript(sconsScriptA, {'instance' : instanceWithAllEnv},
> variant_dir='build/win32', duplicate=0)
> |SConscript(sconsScriptA, {'instance' : instanceWithAllEnv},
> variant_dir='build/win64', duplicate=0)
>
> If possible, I would prefer to do
>
> |SConscript(sconsScriptA, {'instance' : instanceWithAllEnv},
> variant_dir='build', duplicate=0)
>
> Then, sconsScriptA would iterate over win32 and win64 environment and add
> 'win32' or 'win64' string to the variant dir accordingly.
>
> I am pretty sure it is feasible.  But I am not sure it is appropriate.
>
>
>
> --
> View this message in context: http://scons.1086193.n5.
> nabble.com/What-is-the-best-approach-with-SConstruct-calling-SConscript-
> tp40704p40712.html
> Sent from the Users mailing list archive at Nabble.com.
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20161108/2ea14ff2/attachment.html>


More information about the Scons-users mailing list