This hint for setting up python virtual environments came from Nat Linden. I used this procedure. http://timmyreilly.azurewebsites.net/python-pip-virtualenv-installation-on-windows/
As of now I have 3 environments: autobuild-1.0 pip install hg+http://bitbucket.org/lindenlab/autobuild-1.0#egg=autobuild autobuild-1.1 pip install hg+http://bitbucket.org/lindenlab/autobuild-1.1#egg=autobuild FS pip install hg+http://bitbucket.org/NickyD/autobuild-1.0#egg=autobuild As shown above for each you will need its specific autobuild. Then, for example, use "workon FS" to set use of FS autobuild and follow FS build instructions. Just now tried FS -m64 configure and it is complaining about boost being overwriting something that is already present even though configuring from scratch. On Thu, Jan 5, 2017 at 5:59 AM, Nicky Perian <nickyper...@gmail.com> wrote: > Nope. > Only 32. > > From README_BUILD_FIRESTORM_WIN64.txt > > 1.1 Visual Studio 2013 Community Edition or better with installed 64 bit > compiler. > 1.2 Or Visual Studio Express and 'Microsoft Windows SDK for Windows 7 and > .NET Framework 4'. Make sure to install at least the header and compiler > with all the latest service packs. > 2. autobuild from *https://bitbucket.org/NickyD/autobuild-1.0 > <https://bitbucket.org/NickyD/autobuild-1.0>* > 3. FMOD, if you want sound, please see https://bitbucket.org/NickyD/ > 3p-fmodex > > > > On Thu, Jan 5, 2017 at 1:45 AM, Lance Corrimal <lance.corri...@eregion.de> > wrote: > >> Does that autobuild in https://bitbucket.org/lindenlab/autobuild-1.0 >> support -m64? >> >> Am 04.01.2017 um 16:06 schrieb Nicky Perian: >> >> I have never used ssh://h...@bitbucket.org/NickyP/fs-autobuild-1.0. It was >> put there for reference only. >> This is what you should be using https://bitbucket.org/li >> ndenlab/autobuild-1.0 >> >> https://bitbucket.org/kokua/kokua-sl/src/79c54527c3963bce848 >> 484a49a61d82811f20a3c/README?at=default&fileviewer=file- >> view-default#README-263 >> >> That is my dev setup and I was able to build a local FS with that setup. >> But, I had already edited up to autobuild-1.1. That is only used in one >> place at this line. >> https://bitbucket.org/kokua/kokua-sl/src/79c54527c3963bce848 >> 484a49a61d82811f20a3c/README?at=default&fileviewer=file- >> view-default#README-410 >> >> Change autobuild-1.1 to autobuild-1.0 and the instruction should work. >> >> As is most often the case build instructions are a work in progress. >> >> >> On Wed, Jan 4, 2017 at 7:15 AM, Lance Corrimal <lance.corri...@eregion.de >> > wrote: >> >>> d:\Users\lemmy\Build\autobuild-1.0>autobuild --version >>> autobuild 1.0 >>> >>> >>> d:\Users\lemmy\Build\autobuild-1.0>which autobuild >>> /cygdrive/d/Users/lemmy/Build/autobuild-1.0/bin/autobuild >>> >>> d:\Users\lemmy\Build\autobuild-1.0>hg sum >>> Vorgõnger: 728:7c36cb02fc10 tip >>> Search two directories up for package_override, we need this during the >>> VS build steps. >>> Zweig: default >>> ▄bernehme: (clean) >>> Aktualisiere: (aktuell) >>> >>> d:\Users\lemmy\Build\autobuild-1.0>hg in >>> Vergleiche mit ssh://h...@bitbucket.org/NickyP/fs-autobuild-1.0 >>> Suche nach ─nderungen >>> Keine ─nderungen gefunden >>> >>> >>> Am 04.01.2017 um 13:46 schrieb Lance Corrimal: >>> > Am Mittwoch, 4. Januar 2017, 06:23:32 CET schrieb Nicky Perian: >>> >> autobuild --version >>> >> >>> >> s/b 1.0 unless your on the viewer64 repo. >>> >> >>> > 64bit here.. using your autobuild, which used to work just fine before >>> I >>> > reinstalled my PC... >>> > >>> > _______________________________________________ >>> > 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 >>> >>> >> >> >
_______________________________________________ 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
