I haven't confirmed, but there may be an issue with having build-vc120-32 and build-vc120-64 side by side and pickup of library dependencies when switching from one build to the other.
On Wed, Dec 14, 2016 at 7:56 PM, Nat Goodspeed <n...@lindenlab.com> wrote: > On Wed, Dec 14, 2016 at 7:13 PM, Nicky Perian <nickyper...@gmail.com> > wrote: > > While building my own 64 bit fmodex archive I had an issue with "autobuild >> --address-size=64 build". >> autobuild would not build a 64 bit variant. Once I added "export >> AUTOBUILD_PLATFORM_OVERRIDE='darwin64'" I was able to produce the 64 bit >> archive. >> >> I have not repro'ed because once I had the archive I didn't care to go >> back through it. >> > > Two comments... > > First, it appears that autobuild's argument parsing is sensitive to > options before vs. after the subcommand. I always use "autobuild build -A > 64", which works. I don't know why it doesn't work equally well the other > way, but yours is not the first time I've seen a similar complaint. > > Second, I'm glad that the fmodex build responded well to the override. > Just last week I had to tweak the build-cmd.sh scripts for both jsoncpp and > breakpad because their build systems were not forwarding the architecture > or address size properly, and the "darwin64" build was still producing > 32-bit libraries. I'm not yet convinced that we've seen the last of that > issue; just be aware that that might be the cause of observed problems. >
_______________________________________________ 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
