Re: [opensource-dev] 64 bit viewers build instructions

2016-12-22 Thread Nicky Perian
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  wrote:

> On Wed, Dec 14, 2016 at 7:13 PM, Nicky Perian 
> 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

Re: [opensource-dev] 64 bit viewers build instructions

2016-12-22 Thread Nat Goodspeed
On Thu, Dec 22, 2016 at 8:29 AM, Nicky Perian  wrote:

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.
>

Please let us know what you find out.

In general, we have tried to isolate build artifacts under the
build-whatever directory, in this case build-vc120-32 or build-vc120-64.
That includes the libraries installed by autobuild: there should be
separate build-vc120-32/packages and build-vc120-64/packages
subdirectories. That separation should (!) also include CMake byproducts --
though if indeed there's some unintentional crossover, I would suspect
CMake stuff.

Don't be dismayed if, when you post your findings, we don't respond right
away: today is the last day before Linden's holiday break. We'll be back
online, much refreshed, on Tuesday, January 3rd.

Merry Christmas!
___
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

Re: [opensource-dev] 64 bit viewers build instructions

2016-12-22 Thread Oz Linden (Scott Lawrence)

On 2016-12-22 09:58 , Nat Goodspeed wrote:


In general, we have tried to isolate build artifacts under the 
build-whatever directory, in this case build-vc120-32 or 
build-vc120-64. That includes the libraries installed by autobuild: 
there should be separate build-vc120-32/packages and 
build-vc120-64/packages subdirectories. That separation should (!) 
also include CMake byproducts -- though if indeed there's some 
unintentional crossover, I would suspect CMake stuff.
Be alert for anything that's starting searches relative to the 
CMAKE_SOURC_DIR/..



--
OZ LINDEN | Engineering Director, Second Life
email or hangouts: o...@lindenlab.com  | Real 
Life: Scott Lawrence

LINDEN LAB | Create Virtual Experiences 
___
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

Re: [opensource-dev] 64 bit viewers build instructions

2016-12-22 Thread Nicky Perian
This is from viewer64 repo w/o changes.
0>c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(51): error
C2226: syntax error : unexpected type 'S'
(C:\Users\Bill\P64\viewer64pure\build-vc120-64\packages\llphysicsextensions\stub\LLPhysicsExtensionsStubImpl.cpp)
10>  c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(52)
: see reference to class template instantiation 'LLResultTypeAdd'
being compiled
10>c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(51): error
C2226: syntax error : unexpected type 'S'
(C:\Users\Bill\P64\viewer64pure\build-vc120-64\packages\llphysicsextensions\stub\LLPathingLibStubImpl.cpp)
10>  c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(52)
: see reference to class template instantiation 'LLResultTypeAdd'
being compiled
10>c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(51): error
C3646: 'type_t' : unknown override specifier
(C:\Users\Bill\P64\viewer64pure\build-vc120-64\packages\llphysicsextensions\stub\LLPhysicsExtensionsStubImpl.cpp)
10>c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(51): error
C3646: 'type_t' : unknown override specifier
(C:\Users\Bill\P64\viewer64pure\build-vc120-64\packages\llphysicsextensions\stub\LLPathingLibStubImpl.cpp)
10>c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(51): error
C4430: missing type specifier - int assumed. Note: C++ does not support
default-int
(C:\Users\Bill\P64\viewer64pure\build-vc120-64\packages\llphysicsextensions\stub\LLPhysicsExtensionsStubImpl.cpp)
10>c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(51): error
C4430: missing type specifier - int assumed. Note: C++ does not support
default-int
(C:\Users\Bill\P64\viewer64pure\build-vc120-64\packages\llphysicsextensions\stub\LLPathingLibStubImpl.cpp)
1

I suspected that I had stepped on my source so started with a fresh clone.
This kicks off pages of the same error.

On Thu, Dec 22, 2016 at 9:22 AM, Oz Linden (Scott Lawrence) <
o...@lindenlab.com> wrote:

> On 2016-12-22 09:58 , Nat Goodspeed wrote:
>
>
> In general, we have tried to isolate build artifacts under the
> build-whatever directory, in this case build-vc120-32 or build-vc120-64.
> That includes the libraries installed by autobuild: there should be
> separate build-vc120-32/packages and build-vc120-64/packages
> subdirectories. That separation should (!) also include CMake byproducts --
> though if indeed there's some unintentional crossover, I would suspect
> CMake stuff.
>
> Be alert for anything that's starting searches relative to the
> CMAKE_SOURC_DIR/..
>
>
> --
> OZ LINDEN | Engineering Director, Second Life
> email or hangouts: o...@lindenlab.com | Real Life: Scott Lawrence
> LINDEN LAB | Create Virtual Experiences 
>
___
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

Re: [opensource-dev] 64 bit viewers build instructions

2016-12-22 Thread Nat Goodspeed
On Thu, Dec 22, 2016 at 12:21 PM, Nicky Perian 
wrote:

This is from viewer64 repo w/o changes.
> 0>c:\users\bill\p64\viewer64pure\indra\llcommon\llunittype.h(51): error
> C2226: syntax error : unexpected type 'S' (C:\Users\Bill\P64\
> viewer64pure\build-vc120-64\packages\llphysicsextensions\stub\
> LLPhysicsExtensionsStubImpl.cpp)
>

Okay. We're trying to unify compile switches across libraries and viewer
builds, so we've introduced
https://bitbucket.org/lindenlab/viewer-build-variables
rather than trying to keep compile switches in sync by hand, which has
historically been troublesome.

The idea is that you clone that repo locally, then set environment variable
AUTOBUILD_VARIABLES_FILE to the 'variables' file within your local
viewer-build-variables clone.

This provides switches and macro definitions that we've previously set in
indra/cmake/00-Common.cmake. In fact I recently pulled the LL_BUILD
environment variable (set by autobuild source_environment when
AUTOBUILD_VARIABLES_FILE is set) into the CMake logic, and eliminated the
switches within 00-Common.cmake now made redundant by the switches in
LL_BUILD.

Among those switches is /DLL_WINDOWS. At this point, if you don't have
AUTOBUILD_VARIABLES_FILE pointing to your local
viewer-build-variables/variables file, you won't have LL_WINDOWS set.

Without LL_WINDOWS, you don't get LL_TYPEOF() defined.

Without LL_TYPEOF(), you get those strange errors.

Naturally we'll be updating all the public documentation to reflect these
things... but we're still evolving all this stuff! Sorry, but by tracking
the bleeding edge of our development, you might occasionally get nicked.
___
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

Re: [opensource-dev] 64 bit viewers build instructions

2016-12-22 Thread Nicky Perian
I have a local repo of
https://bitbucket.org/lindenlab/viewer-build-variables as a sibling of
viewer64.
Just now pulled and updated it.
AUTOBUILD_VARIABLES_FILE=C:\Users\Bill\P64\viewer-build-variables\variables
has been set system wide.
Within my configure script (a windows batch file) is autobuild
source_environment and
​autobuild configure

I configure then open vs2013 and the errors continue as before.

Don't need to pursue til after holidays.

Merry Christmas!!

Nicky
___
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

Re: [opensource-dev] 64 bit viewers build instructions

2016-12-22 Thread Nat Goodspeed
On Thu, Dec 22, 2016 at 2:24 PM, Nicky Perian  wrote:

> AUTOBUILD_VARIABLES_FILE=C:\Users\Bill\P64\viewer-build-variables\variables
> has been set system wide.
> Within my configure script (a windows batch file) is autobuild
> source_environment and
> autobuild configure
>
> I configure then open vs2013 and the errors continue as before.

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.

> Merry Christmas!!

You too! And to all a good night!
___
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