On May 4, 2017 4:49 PM, "Mats Wichmann" <mats at wichmann.us> wrote:
#1, if you use the env.Function() form of something, it implies you're
passing env, right?
I'm wondering because I see this construct:
connectivity_env.SConscript('#common/SConscript'), exports =
'connectivity_env')
is the exports part in this invocation redundant?
#2, it seems scripts call other scripts (especially ones in extlibs) to
make sure some dependency is in place, and occasionally to fetch some
related variables. But it seems to me you should only need to do this
once... if such subsidiary SConscripts properly export any needed things
that should appear in the global environment.
just out of curiosity - I'm _not_ whining, really! - has the idea of moving
to a standard scons setup been dropped? e.g. using site_scons, etc. that
would solve a lot of problems.
gregg
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170504/9f6ce4eb/attachment.html>
