On Tue, May 31, 2016 at 12:24 PM, Nash, George <george.nash at intel.com> wrote:
> This comes down to one of the core design ideas of SCons. A scons script > should be able to run on any system regardless of the environmental state > of that system. For this reason scons starts up a subshell and discards > ALL environment variables. This can be annoying since it can cause scons > to not find things that are specified in the PATH environment variable. > In general you should specify the build option on the command line. There > are ways to work around this but it requires a developer taking the time to > specify in the scons script which environment variables are not going to > get discarded. It must be done for each and every environment variable and > it should also default to the command line value if it is specified. > Thanks. I can live with the command line, but I think it would be a good idea to mention this little factoid in the build instructions. I suspect most people will make the same assumption I made, that such vars can be put in the environment. -Gregg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160531/1e79aafc/attachment.html>
