>>The autobuild feature that implicitly expands environment variables such as $AUTOBUILD_ADDRSIZE >>appearing in autobuild.xml is relatively recent, and we probably haven't yet covered all the cases where that >>should happen.
As far as i can tell this happens only on 32 bit builds. On Sat, Feb 18, 2017 at 3:11 PM, Nat Goodspeed <n...@lindenlab.com> wrote: > On Feb 18, 2017 1:33 PM, "Nicky Perian" <nickyper...@gmail.com> wrote: > > Any idea why autobuild the looks in the wrong location for > installed-packages.xml? > > ========== Build: 5 succeeded, 0 failed, 29 up-to-date, 2 skipped > ========== > metadata file name: autobuild-package.xml > built Second Life Viewer version 5.1.0.41141 > installed files in installed-packages.xml > no installed files found (C:\Users\Bill\P64\Kokua-SL-64 > \build-vc120-$AUTOBUILD_ADDRSIZE\packages\installed-packages.xml) > > > The autobuild feature that implicitly expands environment variables such > as $AUTOBUILD_ADDRSIZE appearing in autobuild.xml is relatively recent, and > we probably haven't yet covered all the cases where that should happen. > > The initial implementation expanded variables right at the point when > autobuild.xml is read, so the expansions applied EVERYWHERE. That turned > out to be the wrong approach, since a number of autobuild commands rewrite > autobuild.xml. We found, to our dismay, that after any such command, all > the variables had been replaced with the specific value at that moment - > making the parameterization useless. > > So now we expand variables in specific subcommands. I'm sure we don't yet > do that everywhere we should. >
_______________________________________________ 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
