I was expecting to build from the windows command prompt. I can go into
Cygwin64 terminal and
eval "$(autobuild source_environment)" appears to run, but doesn't feedback
any information that it has.
Then in the windows command prompt terminal a virtualenv is set to
autobuild-1.1 and trying to execu
On Thu, Jan 5, 2017 at 4:41 PM, Nicky Perian 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_M
>>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 -
On Wed, Jan 4, 2017 at 7:43 PM, Nicky Perian wrote:
>I'll make the CMake logic die with an error if it doesn't see the
> >LL_BUILD environment variable. That will at least be less obscure than
> >"unexpected type 'S'", and may help identify the problem you're
> >encountering.
>
> I'm back. Still
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=auto
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
