On Thu, Jan 5, 2017 at 4:41 PM, Nicky Perian <nickyper...@gmail.com> wrote:
>>I do not have enough information to know where in your build environment > the disconnect lies. > autobuild source_environment 2>&1 |c:\cygwin64\bin\tee configRel.log > autobuild --address-size=64 configure -c ReleaseOS -- > -DCMAKE_VERBOSE_MAKEFILE:BOOL=FALSE -DLL_TESTS:BOOL=OFF > -DPACKAGE:BOOL=FALSE -DOPENAL:BOOL=FALSE -DFMODEX:BOOL=TRUE 2>&1 > |c:\cygwin64\bin\tee -a configRel.log > I could be misinterpreting; you could simply be running the above commands for purposes of creating this mail message. But if this is the command sequence you actually use to configure and build, then autobuild source_environment is not affecting the running environment. autobuild source_environment does not (cannot) directly modify the parent shell's environment variables. It simply writes to its stdout a sequence of variable assignments in bash syntax to be interpreted by the parent shell. You can achieve that either by something like: eval "$(autobuild source_environment)" or something more like: varsfile="$(mktemp -t vars.XXXXXXXX)" autobuild source_environment > "$varsfile" source "$varsfile" You might consider temporarily adding a command such as: echo "LL_BUILD = '$LL_BUILD'" to ensure that the autobuild source_environment command is in fact having the desired effect.
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
