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

[Bill Deegan]

Not the way I would do it, but it's o.k.

On Thu, Nov 10, 2016 at 6:05 PM, Pierre-Luc Boily <pierreluc.boily at gmail.com
> wrote:

> I am still setting part of variant_dir from SConstruct :
>
> |SConscript(sconsScriptA, {'instance' : instanceWithAllEnv},
> variant_dir='build', duplicate=0)
>
> Let see what would like my SConscript :
>
> Import('instance')
>
> win32Env = instance.getWin32Env.Clone()
> win64Env = instance.getWin64Env.Clone()
>
> win32Env.Library('win32\\myLib', 'file.cpp') #final variant dir for win32
> will be build\win32
> win64Env.Library('win64\\myLib', 'file.cpp') #final variant dir for win64
> will be build\win64
>
> So, the benefit of trying to do the above is I still want my SConstruct
> looping over all SConscript without knowing anything about them.  He
> specified only 'build' as variant_dir and SConscript add the final win32 or
> win64 subfolder.
>
> Is it clean to do that?
>
> Thx
>
>
>
> --
> View this message in context: http://scons.1086193.n5.
> nabble.com/What-is-the-best-approach-with-SConstruct-calling-SConscript-
> tp40704p40721.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/20161110/8bf9ef3b/attachment.html>