Re: [opensource-dev] Windows 64 bit build issue

[Callum Prentice (Callum)]

Great. I had an idea that was the case. Thanks again Cinder.

On Wed, Nov 30, 2016 at 6:30 PM, Cinder Roxley 
wrote:

> We nuked that whole project and set volume directly on Windows using
> waveOutSetVolume(HWAVEOUT, DWORD).
> https://bitbucket.org/alchemyviewer/alchemy/commits/
> b3e54a075de4440390bb1be8c9f73bfd94053a01
>
> The shim is only needed up to XP and is completely unnecessary with the
> availability of WASAPI in Vista and above.
>
> --
> Cinder Roxley
> Sent with Airmail
>
> On November 30, 2016 at 7:36:24 PM, Callum Linden (cal...@lindenlab.com)
> wrote:
>
> Thanks so much for the speedy reply Cinder. I hoped that was the case and
> the build seems okay without it.
>
> The other perplexing one is for the winmm_shim project. For 64 bit builds
> it fails with a bunch of unresolved externals which look to be related to
> MMX intrinsic maybe. Not at my computer right now and haven't really
> started to investigate but if that rings s bell after your work, please do
> let me know.
>
> Cheers!
>
> On Nov 30, 2016, at 5:16 PM, Cinder Roxley 
> wrote:
>
> It’s not needed. We dropped it in Alchemy when adding 64-bit support, and
> it continues to run fine. /FIXED:NO just ensures that code can be position
> independent. Maybe at some point this was needed a long time ago for apr
> hijinks or Windows98 compatibility or something of that nature, but you can
> safely remove it.
>
> --
> Cinder Roxley
> Sent with Airmail
>
> On November 30, 2016 at 6:55:37 PM, Callum Prentice (Callum) (
> cal...@lindenlab.com) wrote:
>
> I'm working with Nat Linden on the 64 bit viewer build and we've been
> encountering an odd error - A number of projects in 64 bit only
> configurations have an entry for "Force Includes" files set to XED:NO.
> Nothing on Google so we were stumped for a while but eventually tracked it
> down to a number of lines in CMakeLists.txt files of the form:
> *add_definitions(/FIXED:NO)*. Evidently, */FI* is the compiler command to
> include a forced header file - hence the *XED:NO* entry. You can see one
> here: https://bitbucket.org/lindenlab/viewer64/src/
> 3f7ba2a06e5cea596e3a4006d57e3fbc4703d90f/indra/llcommon/
> CMakeLists.txt?at=default=file-view-default#CMakeLists.txt-248
>
> The *FIXED* command is evidently for the linker and not the compiler but
> I'm not sure (a) if it's needed or (b) if it is, how to direct it at the
> right place.
>
> Has anyone else encountered this and already and figured it out?
>
> --
>
> ​Callum Prentice
> | Software Engineer
>
> 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
>
>


-- 

CALLUM PRENTICE | Software Engineer

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] Windows 64 bit build issue

[Cinder Roxley]

We nuked that whole project and set volume directly on Windows using 
waveOutSetVolume(HWAVEOUT, DWORD).
https://bitbucket.org/alchemyviewer/alchemy/commits/b3e54a075de4440390bb1be8c9f73bfd94053a01

The shim is only needed up to XP and is completely unnecessary with the 
availability of WASAPI in Vista and above.
 
 
-- 
Cinder Roxley
Sent with Airmail
 

On November 30, 2016 at 7:36:24 PM, Callum Linden (cal...@lindenlab.com 
 ) wrote:

 
Thanks so much for the speedy reply Cinder. I hoped that was the case and the 
build seems okay without it. 

The other perplexing one is for the winmm_shim project. For 64 bit builds it 
fails with a bunch of unresolved externals which look to be related to MMX 
intrinsic maybe. Not at my computer right now and haven't really started to 
investigate but if that rings s bell after your work, please do let me know. 

Cheers! 

On Nov 30, 2016, at 5:16 PM, Cinder Roxley  > wrote:

It’s not needed. We dropped it in Alchemy when adding 64-bit support, and it 
continues to run fine. /FIXED:NO just ensures that code can be position 
independent. Maybe at some point this was needed a long time ago for apr 
hijinks or Windows98 compatibility or something of that nature, but you can 
safely remove it.

-- 
Cinder Roxley
Sent with Airmail

On November 30, 2016 at 6:55:37 PM, Callum Prentice (Callum) 
(cal...@lindenlab.com  ) wrote:

I'm working with Nat Linden on the 64 bit viewer build and we've been 
encountering an odd error - A number of projects in 64 bit only configurations 
have an entry for "Force Includes" files set to XED:NO.  Nothing on Google so 
we were stumped for a while but eventually tracked it down to a number of lines 
in CMakeLists.txt files of the form: add_definitions(/FIXED:NO). Evidently, /FI 
is the compiler command to include a forced header file - hence the XED:NO 
entry. You can see one here: 
https://bitbucket.org/lindenlab/viewer64/src/3f7ba2a06e5cea596e3a4006d57e3fbc4703d90f/indra/llcommon/CMakeLists.txt?at=default=file-view-default#CMakeLists.txt-248

The FIXED command is evidently for the linker and not the compiler but I'm not 
sure (a) if it's needed or (b) if it is, how to direct it at the right place.

Has anyone else encountered this and already and figured it out?

--

​Callum Prentice
| Software Engineer

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

___
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] Windows 64 bit build issue

[Callum Linden]

Thanks so much for the speedy reply Cinder. I hoped that was the case and the 
build seems okay without it. 

The other perplexing one is for the winmm_shim project. For 64 bit builds it 
fails with a bunch of unresolved externals which look to be related to MMX 
intrinsic maybe. Not at my computer right now and haven't really started to 
investigate but if that rings s bell after your work, please do let me know. 

Cheers! 

> On Nov 30, 2016, at 5:16 PM, Cinder Roxley  wrote:
> 
> It’s not needed. We dropped it in Alchemy when adding 64-bit support, and it 
> continues to run fine. /FIXED:NO just ensures that code can be position 
> independent. Maybe at some point this was needed a long time ago for apr 
> hijinks or Windows98 compatibility or something of that nature, but you can 
> safely remove it.
> 
> -- 
> Cinder Roxley
> Sent with Airmail
> 
>> On November 30, 2016 at 6:55:37 PM, Callum Prentice (Callum) 
>> (cal...@lindenlab.com) wrote:
>> 
>> I'm working with Nat Linden on the 64 bit viewer build and we've been 
>> encountering an odd error - A number of projects in 64 bit only 
>> configurations have an entry for "Force Includes" files set to XED:NO.  
>> Nothing on Google so we were stumped for a while but eventually tracked it 
>> down to a number of lines in CMakeLists.txt files of the form: 
>> add_definitions(/FIXED:NO). Evidently, /FI is the compiler command to 
>> include a forced header file - hence the XED:NO entry. You can see one here: 
>> https://bitbucket.org/lindenlab/viewer64/src/3f7ba2a06e5cea596e3a4006d57e3fbc4703d90f/indra/llcommon/CMakeLists.txt?at=default=file-view-default#CMakeLists.txt-248
>> 
>> The FIXED command is evidently for the linker and not the compiler but I'm 
>> not sure (a) if it's needed or (b) if it is, how to direct it at the right 
>> place.
>> 
>> Has anyone else encountered this and already and figured it out?
>> 
>> --
>> ​Callum Prentice | 
>> Software Engineer
>> 
>> 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
___
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] Windows 64 bit build issue

[Cinder Roxley]

It’s not needed. We dropped it in Alchemy when adding 64-bit support, and it 
continues to run fine. /FIXED:NO just ensures that code can be position 
independent. Maybe at some point this was needed a long time ago for apr 
hijinks or Windows98 compatibility or something of that nature, but you can 
safely remove it.
 
 
-- 
Cinder Roxley
Sent with Airmail
 

On November 30, 2016 at 6:55:37 PM, Callum Prentice (Callum) 
(cal...@lindenlab.com  ) wrote:

 
I'm working with Nat Linden on the 64 bit viewer build and we've been 
encountering an odd error - A number of projects in 64 bit only configurations 
have an entry for "Force Includes" files set to XED:NO.  Nothing on Google so 
we were stumped for a while but eventually tracked it down to a number of lines 
in CMakeLists.txt files of the form: add_definitions(/FIXED:NO). Evidently, /FI 
is the compiler command to include a forced header file - hence the XED:NO 
entry. You can see one here: 
https://bitbucket.org/lindenlab/viewer64/src/3f7ba2a06e5cea596e3a4006d57e3fbc4703d90f/indra/llcommon/CMakeLists.txt?at=default=file-view-default#CMakeLists.txt-248

The FIXED command is evidently for the linker and not the compiler but I'm not 
sure (a) if it's needed or (b) if it is, how to direct it at the right place.

Has anyone else encountered this and already and figured it out?

--

​Callum Prentice
| Software Engineer

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

___
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

[opensource-dev] Windows 64 bit build issue

[Callum Prentice (Callum)]

I'm working with Nat Linden on the 64 bit viewer build and we've been
encountering an odd error - A number of projects in 64 bit only
configurations have an entry for "Force Includes" files set to XED:NO.
Nothing on Google so we were stumped for a while but eventually tracked it
down to a number of lines in CMakeLists.txt files of the form:
*add_definitions(/FIXED:NO)*. Evidently, */FI* is the compiler command to
include a forced header file - hence the *XED:NO* entry. You can see one
here:
https://bitbucket.org/lindenlab/viewer64/src/3f7ba2a06e5cea596e3a4006d57e3fbc4703d90f/indra/llcommon/CMakeLists.txt?at=default=file-view-default#CMakeLists.txt-248

The *FIXED* command is evidently for the linker and not the compiler but
I'm not sure (a) if it's needed or (b) if it is, how to direct it at the
right place.

Has anyone else encountered this and already and figured it out?

-- 

​Callum Prentice
| Software Engineer

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

[Monty Brandenberg]

On 11/30/2016 4:11 PM, Nat Goodspeed wrote:
>
> I think we decided back when switching to VS 2013 that /GL and /LTCG
> didn't add enough value for us to bother with them. I think the
> expedient fix would be to remove /GL from jpeglib.

I'll be the grumpy engineer and ask that 00-COMPILE-LINK-RUN.txt
in the cmake directory get updated with current options and the
thinking that led to them...

m

-- 
Monty Brandenberg | Unit of Production
Skype monty.linden | Second Life Monty Linden

Linden Lab | Makers of Shared Creative Spaces
Check out what we're working on!
___
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

[Nicky Perian]

Disregard, It was a viewer cmake for llimagej2coj
that did not work.

${OPENJPEG_LIBRARIES}
 )
+if (WINDOWS)
+  set_target_properties(
+llimagej2coj
+PROPERTIES
+LINK_FLAGS "/MANIFEST:NO /SAFESEH:NO /LTCG /NODEFAULTLIB:LIBCMT"
+LINK_FLAGS_DEBUG "/MANIFEST:NO /SAFESEH:NO /NODEFAULTLIB:LIBCMTD"
+)
+endif (WINDOWS)
\ No newline at end of file



On Wed, Nov 30, 2016 at 3:48 PM, Nicky Perian  wrote:

> >> Is it just a question of add /LTCG to the jpeglib link command?
>
> I tired that and it didn't change anything.
>
>
> On Wed, Nov 30, 2016 at 3:04 PM, Callum Prentice (Callum) <
> cal...@lindenlab.com> wrote:
>
>> I'd like to fix that too.
>>
>> Is it just a question of add /LTCG to the jpeglib link command?  I see
>> that's done via an nmake makefile and then build via a .sln but I think I
>> see where to add that command.
>>
>> On Wed, Nov 30, 2016 at 5:53 AM, Nicky Perian 
>> wrote:
>>
>>> Would this be a good time to fix this warning?
>>>
>>>   jpeglib.lib(jerror.obj) : MSIL .netmodule or module compiled with /GL
>>> found; restarting link with /LTCG; add /LTCG to the link command line to
>>> improve linker performance
>>>
>>> Thanks
>>>
>>> On Tue, Nov 29, 2016 at 10:30 PM, Nat Goodspeed 
>>> wrote:
>>>
 On Nov 29, 2016 11:11 PM, "Nicky Perian"  wrote:

 > I am unable to get a windows 64 bit build environment. A learning
 issue for me.
 > What commands do you use to switch to 64 bit?

 I use:

 autobuild build --address-size=64

 :-)

 But I don't yet have a clean 64-bit build on any platform.

>>>
>>>
>>> ___
>>> 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
>>>
>>
>>
>>
>> --
>>
>> CALLUM PRENTICE | Software Engineer
>>
>> 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

[Nicky Perian]

>> Is it just a question of add /LTCG to the jpeglib link command?

I tired that and it didn't change anything.


On Wed, Nov 30, 2016 at 3:04 PM, Callum Prentice (Callum) <
cal...@lindenlab.com> wrote:

> I'd like to fix that too.
>
> Is it just a question of add /LTCG to the jpeglib link command?  I see
> that's done via an nmake makefile and then build via a .sln but I think I
> see where to add that command.
>
> On Wed, Nov 30, 2016 at 5:53 AM, Nicky Perian 
> wrote:
>
>> Would this be a good time to fix this warning?
>>
>>   jpeglib.lib(jerror.obj) : MSIL .netmodule or module compiled with /GL
>> found; restarting link with /LTCG; add /LTCG to the link command line to
>> improve linker performance
>>
>> Thanks
>>
>> On Tue, Nov 29, 2016 at 10:30 PM, Nat Goodspeed 
>> wrote:
>>
>>> On Nov 29, 2016 11:11 PM, "Nicky Perian"  wrote:
>>>
>>> > I am unable to get a windows 64 bit build environment. A learning
>>> issue for me.
>>> > What commands do you use to switch to 64 bit?
>>>
>>> I use:
>>>
>>> autobuild build --address-size=64
>>>
>>> :-)
>>>
>>> But I don't yet have a clean 64-bit build on any platform.
>>>
>>
>>
>> ___
>> 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
>>
>
>
>
> --
>
> CALLUM PRENTICE | Software Engineer
>
> 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

[Nat Goodspeed]

On Wed, Nov 30, 2016 at 4:04 PM, Callum Prentice (Callum) <
cal...@lindenlab.com> wrote:

Is it just a question of add /LTCG to the jpeglib link command?  I see
> that's done via an nmake makefile and then build via a .sln but I think I
> see where to add that command.
>

I think we decided back when switching to VS 2013 that /GL and /LTCG didn't
add enough value for us to bother with them. I think the expedient fix
would be to remove /GL from jpeglib.
___
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

[Callum Prentice (Callum)]

I'd like to fix that too.

Is it just a question of add /LTCG to the jpeglib link command?  I see
that's done via an nmake makefile and then build via a .sln but I think I
see where to add that command.

On Wed, Nov 30, 2016 at 5:53 AM, Nicky Perian  wrote:

> Would this be a good time to fix this warning?
>
>   jpeglib.lib(jerror.obj) : MSIL .netmodule or module compiled with /GL
> found; restarting link with /LTCG; add /LTCG to the link command line to
> improve linker performance
>
> Thanks
>
> On Tue, Nov 29, 2016 at 10:30 PM, Nat Goodspeed  wrote:
>
>> On Nov 29, 2016 11:11 PM, "Nicky Perian"  wrote:
>>
>> > I am unable to get a windows 64 bit build environment. A learning issue
>> for me.
>> > What commands do you use to switch to 64 bit?
>>
>> I use:
>>
>> autobuild build --address-size=64
>>
>> :-)
>>
>> But I don't yet have a clean 64-bit build on any platform.
>>
>
>
> ___
> 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
>



-- 

CALLUM PRENTICE | Software Engineer

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

[Nicky Perian]

Would this be a good time to fix this warning?

  jpeglib.lib(jerror.obj) : MSIL .netmodule or module compiled with /GL
found; restarting link with /LTCG; add /LTCG to the link command line to
improve linker performance

Thanks

On Tue, Nov 29, 2016 at 10:30 PM, Nat Goodspeed  wrote:

> On Nov 29, 2016 11:11 PM, "Nicky Perian"  wrote:
>
> > I am unable to get a windows 64 bit build environment. A learning issue
> for me.
> > What commands do you use to switch to 64 bit?
>
> I use:
>
> autobuild build --address-size=64
>
> :-)
>
> But I don't yet have a clean 64-bit build on any platform.
>
___
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