subject:"\[opensource\-dev\] Viewer Tools Upgrades \- with a call for help"


On 2015-02-04 11:27 , Nicky Perian wrote:
Yes, I am being persistent and I will not let it drop til I get a 
definitive answer from Linden Lab.




Ok - if any of the following sounds harsh, it's not meant to be, and it 
should not be taken as critical of anyone - it's written this way so 
that it will be as clear and definitive as I can be:


 * Look at what we do in the 'Release' configuration.
   We want open source builds to be as close to that as we can possibly
   make them (because it maximizes the chances we can use contributions
   easily).
 * We do not care about and will not accept changes to support building
   with more than one version of Visual Studio.
   If a case can be made that there is a better choice than the
   Community Edition, feel free to make it but pending that case being
   made that's the choice.
 * How TPVs that are not following our build system evolution and have
   not been for some time are doing things is not of interest.

Is there any more clarity needed?

I and my team have been somewhat disconnected lately doing our 
not-really-sekrit planning sessions, but they're done (I'm writing this 
on the plane home); we'll try to get re-engaged on the issues of getting 
any required changes made. We appreciate your patience.


--
*Oz Linden (Scott Lawrence)* | /Engineering Director, Second Life/
Email or Hangouts o...@lindenlab.com  | Second 
Life Oz 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] Viewer Tools Upgrades - with a call for help


On 2015-02-05 08:39 , Jonathan Welch wrote:

A few more configuration notes/issues:

Autobuild is installed into Python27/scripts -- can this be moved out
of that package's tree?

No, that's where Python wants it.

Autobuild is being fetched from Oz's bitbucket repository -- this
should be moved to a generic lindenlab location.
In time, it will be, but not until we've completed the transition to 
using the new version everywhere.


--
*Oz Linden (Scott Lawrence)* | /Engineering Director, Second Life/
Email or Hangouts o...@lindenlab.com  | Second 
Life Oz 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] Viewer Tools Upgrades - with a call for help


On 2015-02-07 14:24 , Cinder Roxley wrote:

The change would be transparent for the user other than saving them a 
small amount of space on their hard drive. I have no idea what the 
final size of lscript is when compiled, but it’s basically all dead 
and broken code and has been for several years.




If that's true, by all means let's kill it.

--
*Oz Linden (Scott Lawrence)* | /Engineering Director, Second Life/
Email or Hangouts o...@lindenlab.com  | Second 
Life Oz 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] Viewer Tools Upgrades - with a call for help

2015-02-07 Thread Cinder Roxley

On February 7, 2015 at 3:13:31 PM, Oz Linden (Scott Lawrence) 
(o...@lindenlab.com) wrote:
On 2015-02-06 16:12 , Cinder Roxley wrote:

It would simply things greatly to remove lscript from the viewer completely, 
thereby removing the dependency on flex/bison for building. lscript is unused 
other than a few const values. Several tpvs have dropped lscript from the 
build. (I’ve personally done that in two different tpv projects.)
Is this something Linden Lab would be willing to consider? I’d be happy to do 
the work to remove it if it is.


What would the end user effect be?


The change would be transparent for the user other than saving them a small 
amount of space on their hard drive. I have no idea what the final size of 
lscript is when compiled, but it’s basically all dead and broken code and has 
been for several years.

-- 
Cinder Roxley
Sent with Airmail___
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] Viewer Tools Upgrades - with a call for help


On 2015-02-06 16:12 , Cinder Roxley wrote:

It would simply things greatly to remove lscript from the viewer 
completely, thereby removing the dependency on flex/bison for 
building. lscript is unused other than a few const values. Several 
tpvs have dropped lscript from the build. (I’ve personally done that 
in two different tpv projects.)


Is this something Linden Lab would be willing to consider? I’d be 
happy to do the work to remove it if it is.




What would the end user effect be?

--
*Oz Linden (Scott Lawrence)* | /Engineering Director, Second Life/
Email or Hangouts o...@lindenlab.com  | Second 
Life Oz 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] Viewer Tools Upgrades - with a call for help

2015-02-07 Thread Nicky Perian

Is this going to need a library rebuild to correct?
Adding /LTCG seems to make the build slower.
Is there another solution?

33>  Message template SHA_1 has not changed.
33>  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
33> Creating library
C:/Users/bill/newtools/viewer-tools-update/build-vc120/newview/Release/secondlife-bin.lib
and object
C:/Users/bill/newtools/viewer-tools-update/build-vc120/newview/Release/secondlife-bin.exp
33>  Message template SHA_1 has not changed.
33>  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
33> Creating library
C:/Users/bill/newtools/viewer-tools-update/build-vc120/newview/Release/secondlife-bin.lib
and object
C:/Users/bill/newtools/viewer-tools-update/build-vc120/newview/Release/secondlife-bin.exp

On Thu, Feb 5, 2015 at 3:32 PM, Jonathan Welch  wrote:

> Some timing stats:
>
> VS2010 full build: 25 minutes of which 2 minutes are link time
>
> VS2013 full build: 30 minutes of which 1 minute 35 seconds are link time
>
> This link time might even get a little faster if the bug/issue I
> reported a few hours ago is addressed.
>
___
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] Viewer Tools Upgrades - with a call for help

2015-02-06 Thread Cinder Roxley


On February 6, 2015 at 4:54:10 PM, Nicky Perian (nickyper...@gmail.com) wrote:

The issue was in fact paths. Operating with in the Developer Command Prompt for 
VS2013 requires a path of:
C:\cwgwin64\bin;C:\cygwin64\usr\bin

Reason: coreutils which contains printf and a host of other bash commands 
resides in C:\cygwin64\bin. Flex and Bison are installed in 
C:\cygwin64\usr\bin. 

So from Developer Command Prompt for VS2013 you can reach printf and flex and 
bison.

Now the kicker if you now open the Cygwin64  Terminal the aforementioned 
C:\cygwin64\bin and C:\Cygwin64\usr\bin are mangled by cygwin64's remake of the 
path into the form /cygdrive/c/...
and writes usr/bin;usr/bin in the path which breaks the path in
Cygwin64  Terminal.

If you don't include C:\cygwin64\bin and C:\Cygwin64\usr\bin in the path then 
cygwin64 is smart enough to figure it out and printf works in the Cygwin64  
Terminal but, now it is broken in the Developer Command Prompt for VS2013. 

I'm thinking a workaround for this is to begin each windows batch file with a 
path command the appends C:\cwgwin64\bin;C:\cygwin64\usr\bin but do not put 
those in the system path.
Hi,

It would simply things greatly to remove lscript from the viewer completely, 
thereby removing the dependency on flex/bison for building. lscript is unused 
other than a few const values. Several tpvs have dropped lscript from the 
build. (I’ve personally done that in two different tpv projects.)

Is this something Linden Lab would be willing to consider? I’d be happy to do 
the work to remove it if it is.

-- 
Cinder Roxley
Sent with Airmail

___
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] Viewer Tools Upgrades - with a call for help

2015-02-06 Thread Nicky Perian

The issue was in fact paths. Operating with in the Developer Command Prompt
for VS2013 requires a path of:
C:\cwgwin64\bin;C:\cygwin64\usr\bin

Reason: coreutils which contains printf and a host of other bash commands
resides in C:\cygwin64\bin. Flex and Bison are installed in
C:\cygwin64\usr\bin.

So from Developer Command Prompt for VS2013 you can reach printf and flex
and bison.

Now the kicker if you now open the Cygwin64  Terminal the aforementioned
C:\cygwin64\bin and C:\Cygwin64\usr\bin are mangled by cygwin64's remake of
the path into the form /cygdrive/c/...
and writes usr/bin;usr/bin in the path which breaks the path in
Cygwin64  Terminal.

If you don't include C:\cygwin64\bin and C:\Cygwin64\usr\bin in the path
then cygwin64 is smart enough to figure it out and printf works in the
Cygwin64  Terminal but, now it is broken in the Developer Command Prompt
for VS2013.

I'm thinking a workaround for this is to begin each windows batch file with
a path command the appends C:\cwgwin64\bin;C:\cygwin64\usr\bin but do not
put those in the system path.

On Mon, Feb 2, 2015 at 12:25 PM, Oz Linden (Scott Lawrence) <
o...@lindenlab.com> wrote:

>  On 2015-01-31 17:38 , Nicky Perian wrote:
>
>  Anyone know what causes this on a release build?
> Doesn't stop the build and the installer is still made.
> 3>-- Build started: Project: generate_viewer_version, Configuration:
> Release Win32 --
>  3>  processing
> 3>  'printf' is not recognized as an internal or external command,
> 3>  operable program or batch file.
> 3>C:\Program Files
> (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5):
> error MSB6006: "cmd.exe" exited with code 9009.
>
>  Appears to come from newview/CMakeLists.txt
> source_group("CMake Rules" FILES ViewerInstall.cmake)
>
>  # the viewer_version.txt file created here is for passing to
> viewer_manifest and autobuild
> # the summary.json file is created for the benefit of the TeamCity builds,
> where
> #   it is used to provide descriptive information to the build results page
> add_custom_target(generate_viewer_version ALL
>   COMMAND printf
> '${VIEWER_SHORT_VERSION}.${VIEWER_VERSION_REVISION}' >
> ${CMAKE_CURRENT_BINARY_DIR}/viewer_version.txt
>   COMMAND printf
> '{"Type":"viewer","Version":"${VIEWER_SHORT_VERSION}.${VIEWER_VERSION_REVISION}"}'
> > ${CMAKE_BINARY_DIR}/summary.json
>   COMMENT Generating viewer_version.txt for manifest
> processing
>   )
>
>
> That looks like cmake is trying to run commands in a windows shell rather
> than bash; the printf is a bash command.  This works in our build
> environment. It's possible that it could be replaced with cmake FILE
> commands?
>
> --
>  *Oz Linden (Scott Lawrence)* | *Engineering Director, Second Life*
> Email or Hangouts o...@lindenlab.com | Second Life Oz 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
>
___
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] Viewer Tools Upgrades - with a call for help

Some timing stats:

VS2010 full build: 25 minutes of which 2 minutes are link time

VS2013 full build: 30 minutes of which 1 minute 35 seconds are link time

This link time might even get a little faster if the bug/issue I
reported a few hours ago is addressed.
___
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] Viewer Tools Upgrades - with a call for help

Here is another glitch that should be addressed:

  Unable to read versionfile
'E:/ss/STORM-0/build-vc120/newview/viewer_version.txt'
  Traceback (most recent call last):
File "E:/ss/STORM-0/indra/newview/viewer_manifest.py", line 1210,
in 
  main()
File "E:/ss/STORM-0/indra/newview\..\lib\python\indra\util\llmanifest.py",
line 212, in main
  vf = open(args['versionfile'], 'r')
  IOError: [Errno 2] No such file or directory:
'E:/ss/STORM-0/build-vc120/newview/viewer_version.txt'
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5):
error MSB6006: "cmd.exe" exited with code 1.

On Thu, Feb 5, 2015 at 1:54 PM, Jonathan Welch  wrote:
> This error probably should be addressed:
>
>   Message template SHA_1 has not changed.
>   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
>
> On Thu, Feb 5, 2015 at 11:39 AM, Jonathan Welch  wrote:
>> A few more configuration notes/issues:
>>
>> Autobuild is installed into Python27/scripts -- can this be moved out
>> of that package's tree?
>>
>> Autobuild is being fetched from Oz's bitbucket repository -- this
>> should be moved to a generic lindenlab location.
>>
>> On 2/5/15, Nicky Perian  wrote:
>>> Thanks for the input. Looks like incredibuild only uses msbuild when using
>>> Visual Studio Express. Based on the parameters in the Release section of
>>> autobuild.xml it appears that LL uses devenv.
>>>
>>>
>>>
>>> On Wed, Feb 4, 2015 at 3:53 PM, holydoughnuts 
>>> wrote:
>>>
 On 2/2/2015 1:42 PM, Nicky Perian wrote:
 >
 > Does the underlying builder in LL's automated build system call
 > MSBuild or Devenv?
 >

 For what IncrediBuild does, see
 http://www.incredibuild.com/webhelp/distributing_vs_builds.html - it
 currently calls devenv, unless you force it to use msbuild thru the
 registry.

 buildconsole supports command flags compatible with either, so without
 that front end in place you'll want to watch your logs to make sure the
 commands make sense.
 ___
 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] Viewer Tools Upgrades - with a call for help

This error probably should be addressed:

  Message template SHA_1 has not changed.
  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

On Thu, Feb 5, 2015 at 11:39 AM, Jonathan Welch  wrote:
> A few more configuration notes/issues:
>
> Autobuild is installed into Python27/scripts -- can this be moved out
> of that package's tree?
>
> Autobuild is being fetched from Oz's bitbucket repository -- this
> should be moved to a generic lindenlab location.
>
> On 2/5/15, Nicky Perian  wrote:
>> Thanks for the input. Looks like incredibuild only uses msbuild when using
>> Visual Studio Express. Based on the parameters in the Release section of
>> autobuild.xml it appears that LL uses devenv.
>>
>>
>>
>> On Wed, Feb 4, 2015 at 3:53 PM, holydoughnuts 
>> wrote:
>>
>>> On 2/2/2015 1:42 PM, Nicky Perian wrote:
>>> >
>>> > Does the underlying builder in LL's automated build system call
>>> > MSBuild or Devenv?
>>> >
>>>
>>> For what IncrediBuild does, see
>>> http://www.incredibuild.com/webhelp/distributing_vs_builds.html - it
>>> currently calls devenv, unless you force it to use msbuild thru the
>>> registry.
>>>
>>> buildconsole supports command flags compatible with either, so without
>>> that front end in place you'll want to watch your logs to make sure the
>>> commands make sense.
>>> ___
>>> 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] Viewer Tools Upgrades - with a call for help

A few more configuration notes/issues:

Autobuild is installed into Python27/scripts -- can this be moved out
of that package's tree?

Autobuild is being fetched from Oz's bitbucket repository -- this
should be moved to a generic lindenlab location.

On 2/5/15, Nicky Perian  wrote:
> Thanks for the input. Looks like incredibuild only uses msbuild when using
> Visual Studio Express. Based on the parameters in the Release section of
> autobuild.xml it appears that LL uses devenv.
>
>
>
> On Wed, Feb 4, 2015 at 3:53 PM, holydoughnuts 
> wrote:
>
>> On 2/2/2015 1:42 PM, Nicky Perian wrote:
>> >
>> > Does the underlying builder in LL's automated build system call
>> > MSBuild or Devenv?
>> >
>>
>> For what IncrediBuild does, see
>> http://www.incredibuild.com/webhelp/distributing_vs_builds.html - it
>> currently calls devenv, unless you force it to use msbuild thru the
>> registry.
>>
>> buildconsole supports command flags compatible with either, so without
>> that front end in place you'll want to watch your logs to make sure the
>> commands make sense.
>> ___
>> 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] Viewer Tools Upgrades - with a call for help

2015-02-05 Thread Nicky Perian

Thanks for the input. Looks like incredibuild only uses msbuild when using
Visual Studio Express. Based on the parameters in the Release section of
autobuild.xml it appears that LL uses devenv.



On Wed, Feb 4, 2015 at 3:53 PM, holydoughnuts 
wrote:

> On 2/2/2015 1:42 PM, Nicky Perian wrote:
> >
> > Does the underlying builder in LL's automated build system call
> > MSBuild or Devenv?
> >
>
> For what IncrediBuild does, see
> http://www.incredibuild.com/webhelp/distributing_vs_builds.html - it
> currently calls devenv, unless you force it to use msbuild thru the
> registry.
>
> buildconsole supports command flags compatible with either, so without
> that front end in place you'll want to watch your logs to make sure the
> commands make sense.
> ___
> 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] Viewer Tools Upgrades - with a call for help

https://www.incredibuild.com/frequently-asked-questions-technical.html#q4
Q: Can IncrediBuild be used from the command-line or from build scripts?

A: Yes. IncrediBuild includes a strong command-line interface for building
projects, which can easily be integrated in any script that runs
msdev.exe/devenv.exe to build projects. In fact, BuildConsole.exe supports
the devenv/msdev command line syntax so you would typically only need to
replace the executable name in your script!


On Wed, Feb 4, 2015 at 9:30 PM, Nicky Perian  wrote:

> A look at the options below BuildConsole indicated that devenv is the
> underlying builder.
>
> devenv secondlife.sln /build "Release|Win32"
> would be the underlying command as neither of those options can be used
> with MSBuild.
>
>
> Release
> 
>   build
>   
> arguments
> 
>   SecondLife.sln
> 
> command
> BuildConsole
> options
> 
>   /build
>   "/cfg=Release|Win32"
> 
>   
>   configure
>   
> arguments
> 
>   ..\indra
>   &&
>   ..\indra\tools\vstool\VSTool.exe
>   --solution
>   SecondLife.sln
>   --config
>   Release
>   --startup
>   secondlife-bin
> 
> options
> 
>   -G
>   "Visual Studio 12"
> 
>   
>   name
>   Release
> 
>
> On Wed, Feb 4, 2015 at 5:17 PM, Nicky Perian 
> wrote:
>
>> To complete the record as a couple replies  missed the list
>> git pull / merge from singularity 1-20-2015
>> tip at hash 123ded50
>> by Inusaito Sayori 2015-01-20 16:44:22
>> origin https://github.com/singularity-viewer/SingularityViewer.git
>>  (fetch)
>>
>> the msbuild code was put in as an experiment by Shyotl on December 18.
>> 2014
>>
>> https://github.com/singularity-viewer/SingularityViewer/commit/e57bcea3b648bc13ceeb1a5b53a39d27cf103c30
>>
>> I don't know when he actually pushed his branch but I assume it was after
>> 1-20-2015.
>>
>> So it appears that msbuild has only been in use by Singularity for at
>> most 2 weeks.
>>
>> My point is that devenv has been used for a very long time by Singularity
>> with afaik no bad results.
>>
>> So, no my sources were not well out of date and no I did present a self
>> edited code snip.
>>
>>
>>
>>
>> On Wed, Feb 4, 2015 at 4:13 PM, Cinder Roxley 
>> wrote:
>>
>>> On February 4, 2015 at 2:18:55 PM, Nicky Perian (nickyper...@gmail.com)
>>> wrote:
>>>
>>> I know I'm not the sharpest knife in the draw especially when it come to
>>> python. But, if I am reading this code snip from SingularityViewer
>>> develop.py
>>> correctly a command line build using devenv.com is executed each time
>>> it finds visual studio and does not use it for Express because it isn't
>>> present in Express.
>>> {code}
>>> environment = self.find_visual_studio()
>>> if environment == '':
>>> environment = self.find_visual_studio_express()
>>> if environment == '':
>>> environment = self.find_visual_studio_express_single()
>>> if environment == '':
>>> print >> sys.stderr, "Something went very wrong
>>> during build stage, could not find a Visual Studio?"
>>> else:
>>> build_dirs=self.build_dirs()
>>> print >> sys.stderr, "\nSolution generation
>>> complete, it can can now be found in:", build_dirs[0]
>>> print >> sys.stderr, "\nAs you are using an Express
>>> Visual Studio, the build step cannot be automated"
>>> print >> sys.stderr, "\nPlease see
>>> https://wiki.secondlife.com/wiki/Microsoft_Visual_Studio#Extra_steps_for_Visual_Studio_Express_editions
>>>  for Visual Studio Express specific information"
>>> exit(0)
>>>
>>>
>>> Either you’ve intentionally removed msbuild from this block of code or
>>> your sources are well out of date. -_-
>>>
>>> https://bitbucket.org/lkalif/singularityviewer/src/f0b18e52a3d977c2c19f2a6b4e50292acb5941f2/indra/develop.py?at=master#cl-675
>>>
>>> --
>>> Cinder Roxley
>>> Sent with Airmail
>>>
>>>
>>> # devenv.com is CLI friendly, devenv.exe... not so much.
>>> return ('"%sdevenv.com" %s.sln /build %s' %
>>> (self.find_visual_studio(), self.project_name,
>>> self.build_type))
>>> {code}
>>>
>>>
>>> ___
>>> Policies and (un)subscribe information available here:
>>> http://wiki.secondlife.com/wiki/OpenSource-Dev
>>> Please read the policies before posting to keep unmoderated posting
>>> pr

Re: [opensource-dev] Viewer Tools Upgrades - with a call for help

A look at the options below BuildConsole indicated that devenv is the
underlying builder.

devenv secondlife.sln /build "Release|Win32"
would be the underlying command as neither of those options can be used
with MSBuild.


Release

  build
  
arguments

  SecondLife.sln

command
BuildConsole
options

  /build
  "/cfg=Release|Win32"

  
  configure
  
arguments

  ..\indra
  &&
  ..\indra\tools\vstool\VSTool.exe
  --solution
  SecondLife.sln
  --config
  Release
  --startup
  secondlife-bin

options

  -G
  "Visual Studio 12"

  
  name
  Release


On Wed, Feb 4, 2015 at 5:17 PM, Nicky Perian  wrote:

> To complete the record as a couple replies  missed the list
> git pull / merge from singularity 1-20-2015
> tip at hash 123ded50
> by Inusaito Sayori 2015-01-20 16:44:22
> origin https://github.com/singularity-viewer/SingularityViewer.git (fetch)
>
> the msbuild code was put in as an experiment by Shyotl on December 18. 2014
>
> https://github.com/singularity-viewer/SingularityViewer/commit/e57bcea3b648bc13ceeb1a5b53a39d27cf103c30
>
> I don't know when he actually pushed his branch but I assume it was after
> 1-20-2015.
>
> So it appears that msbuild has only been in use by Singularity for at most
> 2 weeks.
>
> My point is that devenv has been used for a very long time by Singularity
> with afaik no bad results.
>
> So, no my sources were not well out of date and no I did present a self
> edited code snip.
>
>
>
>
> On Wed, Feb 4, 2015 at 4:13 PM, Cinder Roxley 
> wrote:
>
>> On February 4, 2015 at 2:18:55 PM, Nicky Perian (nickyper...@gmail.com)
>> wrote:
>>
>> I know I'm not the sharpest knife in the draw especially when it come to
>> python. But, if I am reading this code snip from SingularityViewer
>> develop.py
>> correctly a command line build using devenv.com is executed each time it
>> finds visual studio and does not use it for Express because it isn't
>> present in Express.
>> {code}
>> environment = self.find_visual_studio()
>> if environment == '':
>> environment = self.find_visual_studio_express()
>> if environment == '':
>> environment = self.find_visual_studio_express_single()
>> if environment == '':
>> print >> sys.stderr, "Something went very wrong
>> during build stage, could not find a Visual Studio?"
>> else:
>> build_dirs=self.build_dirs()
>> print >> sys.stderr, "\nSolution generation complete,
>> it can can now be found in:", build_dirs[0]
>> print >> sys.stderr, "\nAs you are using an Express
>> Visual Studio, the build step cannot be automated"
>> print >> sys.stderr, "\nPlease see
>> https://wiki.secondlife.com/wiki/Microsoft_Visual_Studio#Extra_steps_for_Visual_Studio_Express_editions
>>  for Visual Studio Express specific information"
>> exit(0)
>>
>>
>> Either you’ve intentionally removed msbuild from this block of code or
>> your sources are well out of date. -_-
>>
>> https://bitbucket.org/lkalif/singularityviewer/src/f0b18e52a3d977c2c19f2a6b4e50292acb5941f2/indra/develop.py?at=master#cl-675
>>
>> --
>> Cinder Roxley
>> Sent with Airmail
>>
>>
>> # devenv.com is CLI friendly, devenv.exe... not so much.
>> return ('"%sdevenv.com" %s.sln /build %s' %
>> (self.find_visual_studio(), self.project_name,
>> self.build_type))
>> {code}
>>
>>
>> ___
>> 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] Viewer Tools Upgrades - with a call for help

To complete the record as a couple replies  missed the list
git pull / merge from singularity 1-20-2015
tip at hash 123ded50
by Inusaito Sayori 2015-01-20 16:44:22
origin https://github.com/singularity-viewer/SingularityViewer.git (fetch)

the msbuild code was put in as an experiment by Shyotl on December 18. 2014
https://github.com/singularity-viewer/SingularityViewer/commit/e57bcea3b648bc13ceeb1a5b53a39d27cf103c30

I don't know when he actually pushed his branch but I assume it was after
1-20-2015.

So it appears that msbuild has only been in use by Singularity for at most
2 weeks.

My point is that devenv has been used for a very long time by Singularity
with afaik no bad results.

So, no my sources were not well out of date and no I did present a self
edited code snip.




On Wed, Feb 4, 2015 at 4:13 PM, Cinder Roxley 
wrote:

> On February 4, 2015 at 2:18:55 PM, Nicky Perian (nickyper...@gmail.com)
> wrote:
>
> I know I'm not the sharpest knife in the draw especially when it come to
> python. But, if I am reading this code snip from SingularityViewer
> develop.py
> correctly a command line build using devenv.com is executed each time it
> finds visual studio and does not use it for Express because it isn't
> present in Express.
> {code}
> environment = self.find_visual_studio()
> if environment == '':
> environment = self.find_visual_studio_express()
> if environment == '':
> environment = self.find_visual_studio_express_single()
> if environment == '':
> print >> sys.stderr, "Something went very wrong during
> build stage, could not find a Visual Studio?"
> else:
> build_dirs=self.build_dirs()
> print >> sys.stderr, "\nSolution generation complete,
> it can can now be found in:", build_dirs[0]
> print >> sys.stderr, "\nAs you are using an Express
> Visual Studio, the build step cannot be automated"
> print >> sys.stderr, "\nPlease see
> https://wiki.secondlife.com/wiki/Microsoft_Visual_Studio#Extra_steps_for_Visual_Studio_Express_editions
>  for Visual Studio Express specific information"
> exit(0)
>
>
> Either you’ve intentionally removed msbuild from this block of code or
> your sources are well out of date. -_-
>
> https://bitbucket.org/lkalif/singularityviewer/src/f0b18e52a3d977c2c19f2a6b4e50292acb5941f2/indra/develop.py?at=master#cl-675
>
> --
> Cinder Roxley
> Sent with Airmail
>
>
> # devenv.com is CLI friendly, devenv.exe... not so much.
> return ('"%sdevenv.com" %s.sln /build %s' %
> (self.find_visual_studio(), self.project_name,
> self.build_type))
> {code}
>
>
> ___
> 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] Viewer Tools Upgrades - with a call for help

2015-02-04 Thread Cinder Roxley

On February 4, 2015 at 2:18:55 PM, Nicky Perian (nickyper...@gmail.com) wrote:
I know I'm not the sharpest knife in the draw especially when it come to 
python. But, if I am reading this code snip from SingularityViewer develop.py
correctly a command line build using devenv.com is executed each time it finds 
visual studio and does not use it for Express because it isn't present in 
Express.
{code}
        environment = self.find_visual_studio()
        if environment == '':
            environment = self.find_visual_studio_express()
            if environment == '':
                environment = self.find_visual_studio_express_single()
                if environment == '':
                    print >> sys.stderr, "Something went very wrong during 
build stage, could not find a Visual Studio?"
                else:
                    build_dirs=self.build_dirs()
                    print >> sys.stderr, "\nSolution generation complete, it 
can can now be found in:", build_dirs[0]    
                    print >> sys.stderr, "\nAs you are using an Express Visual 
Studio, the build step cannot be automated"
                    print >> sys.stderr, "\nPlease see 
https://wiki.secondlife.com/wiki/Microsoft_Visual_Studio#Extra_steps_for_Visual_Studio_Express_editions
 for Visual Studio Express specific information"
                    exit(0)
    
Either you’ve intentionally removed msbuild from this block of code or your 
sources are well out of date. -_-

https://bitbucket.org/lkalif/singularityviewer/src/f0b18e52a3d977c2c19f2a6b4e50292acb5941f2/indra/develop.py?at=master#cl-675

-- 
Cinder Roxley
Sent with Airmail


        # devenv.com is CLI friendly, devenv.exe... not so much.
        return ('"%sdevenv.com" %s.sln /build %s' % 
                (self.find_visual_studio(), self.project_name, self.build_type))
{code}___
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] Viewer Tools Upgrades - with a call for help

2015-02-04 Thread holydoughnuts

On 2/2/2015 1:42 PM, Nicky Perian wrote:
>
> Does the underlying builder in LL's automated build system call 
> MSBuild or Devenv?
>

For what IncrediBuild does, see 
http://www.incredibuild.com/webhelp/distributing_vs_builds.html - it 
currently calls devenv, unless you force it to use msbuild thru the 
registry.

buildconsole supports command flags compatible with either, so without 
that front end in place you'll want to watch your logs to make sure the 
commands make sense.
___
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] Viewer Tools Upgrades - with a call for help

I know I'm not the sharpest knife in the draw especially when it come to
python. But, if I am reading this code snip from SingularityViewer
develop.py
correctly a command line build using devenv.com is executed each time it
finds visual studio and does not use it for Express because it isn't
present in Express.
{code}
environment = self.find_visual_studio()
if environment == '':
environment = self.find_visual_studio_express()
if environment == '':
environment = self.find_visual_studio_express_single()
if environment == '':
print >> sys.stderr, "Something went very wrong during
build stage, could not find a Visual Studio?"
else:
build_dirs=self.build_dirs()
print >> sys.stderr, "\nSolution generation complete,
it can can now be found in:", build_dirs[0]
print >> sys.stderr, "\nAs you are using an Express
Visual Studio, the build step cannot be automated"
print >> sys.stderr, "\nPlease see
https://wiki.secondlife.com/wiki/Microsoft_Visual_Studio#Extra_steps_for_Visual_Studio_Express_editions
for Visual Studio Express specific information"
exit(0)

# devenv.com is CLI friendly, devenv.exe... not so much.
return ('"%sdevenv.com" %s.sln /build %s' %
(self.find_visual_studio(), self.project_name,
self.build_type))
{code}

On Wed, Feb 4, 2015 at 1:27 PM, Nicky Perian  wrote:

> Yes, I am being persistent and I will not let it drop til I get a
> definitive answer from Linden Lab.
>
> On Wed, Feb 4, 2015 at 10:42 AM, Cinder Roxley 
> wrote:
>
>> On February 4, 2015 at 8:18:19 AM, Nicky Perian (nickyper...@gmail.com)
>> wrote:
>>
>> Underneath BuildConsole which I assume is a wrapper to prepare an
>> internal build request likely calls Devenv or MSBuild. Both are available
>> in Pro and CE. Express only has MSBuild.
>>
>> Building from a blank build-vc120 with Devenv provides a significant
>> build time improvement over MSBuild. However, a note on MS's web page for
>> Denenv indicate that MSBuild should be used. That note has been present
>> since VS2010 release. My thoughts are that the note was there with aim of
>> easing the transition for C# and .NET developers that had historically used
>> MSBuild into C++.
>>
>> One additional point. Singularity Viewer project still uses develop.py
>> and it internally calls devenv.com with no bad result, as far as I know.
>>
>> For the list:
>> Should autobuild.xml call MSBuild or Devenv?
>>
>>
>> Hi,
>>
>> You keep asking this question expecting another response, I guess. As
>> stated both here and on jira, Microsoft recommends MSBuild going forward.
>> All major build server products use MSBuild. Singularity uses MSBuild and
>> only falls back to devenv.exe when MSBuild is not available or broken. VS
>> Express is a dead product as Microsoft will no longer be making new
>> versions of it.
>>
>> VC projects can be slower on MSBuild because it has to do some backflips
>> to build them (they’re not in MSBuild format). MSBuild also supports
>> options that devenv does not (like increased verbosity). Coincidently, the
>> switch from devenv to MSBuild has very little to do with .NET and more to
>> do with the removal of VCBuild on favour of MSBuild. In anything newer than
>> VS2010 devenv just calls MSBuild anyway!
>>
>> Hope this helps.
>>
>> --
>> Cinder Roxley
>> Sent with Airmail
>>
>> ___
>> 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] Viewer Tools Upgrades - with a call for help

Yes, I am being persistent and I will not let it drop til I get a
definitive answer from Linden Lab.

On Wed, Feb 4, 2015 at 10:42 AM, Cinder Roxley 
wrote:

> On February 4, 2015 at 8:18:19 AM, Nicky Perian (nickyper...@gmail.com)
> wrote:
>
> Underneath BuildConsole which I assume is a wrapper to prepare an internal
> build request likely calls Devenv or MSBuild. Both are available in Pro and
> CE. Express only has MSBuild.
>
> Building from a blank build-vc120 with Devenv provides a significant build
> time improvement over MSBuild. However, a note on MS's web page for Denenv
> indicate that MSBuild should be used. That note has been present since
> VS2010 release. My thoughts are that the note was there with aim of easing
> the transition for C# and .NET developers that had historically used
> MSBuild into C++.
>
> One additional point. Singularity Viewer project still uses develop.py and
> it internally calls devenv.com with no bad result, as far as I know.
>
> For the list:
> Should autobuild.xml call MSBuild or Devenv?
>
>
> Hi,
>
> You keep asking this question expecting another response, I guess. As
> stated both here and on jira, Microsoft recommends MSBuild going forward.
> All major build server products use MSBuild. Singularity uses MSBuild and
> only falls back to devenv.exe when MSBuild is not available or broken. VS
> Express is a dead product as Microsoft will no longer be making new
> versions of it.
>
> VC projects can be slower on MSBuild because it has to do some backflips
> to build them (they’re not in MSBuild format). MSBuild also supports
> options that devenv does not (like increased verbosity). Coincidently, the
> switch from devenv to MSBuild has very little to do with .NET and more to
> do with the removal of VCBuild on favour of MSBuild. In anything newer than
> VS2010 devenv just calls MSBuild anyway!
>
> Hope this helps.
>
> --
> Cinder Roxley
> Sent with Airmail
>
> ___
> 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] Viewer Tools Upgrades - with a call for help

2015-02-04 Thread Cinder Roxley

On February 4, 2015 at 8:18:19 AM, Nicky Perian (nickyper...@gmail.com) wrote:
Underneath BuildConsole which I assume is a wrapper to prepare an internal 
build request likely calls Devenv or MSBuild. Both are available in Pro and CE. 
Express only has MSBuild.

Building from a blank build-vc120 with Devenv provides a significant build time 
improvement over MSBuild. However, a note on MS's web page for Denenv indicate 
that MSBuild should be used. That note has been present since VS2010 release. 
My thoughts are that the note was there with aim of easing the transition for 
C# and .NET developers that had historically used MSBuild into C++. 

One additional point. Singularity Viewer project still uses develop.py and it 
internally calls devenv.com with no bad result, as far as I know.

For the list:
Should autobuild.xml call MSBuild or Devenv?


Hi,

You keep asking this question expecting another response, I guess. As stated 
both here and on jira, Microsoft recommends MSBuild going forward. All major 
build server products use MSBuild. Singularity uses MSBuild and only falls back 
to devenv.exe when MSBuild is not available or broken. VS Express is a dead 
product as Microsoft will no longer be making new versions of it.

VC projects can be slower on MSBuild because it has to do some backflips to 
build them (they’re not in MSBuild format). MSBuild also supports options that 
devenv does not (like increased verbosity). Coincidently, the switch from 
devenv to MSBuild has very little to do with .NET and more to do with the 
removal of VCBuild on favour of MSBuild. In anything newer than VS2010 devenv 
just calls MSBuild anyway!

Hope this helps.

-- 
Cinder Roxley
Sent with Airmail___
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] Viewer Tools Upgrades - with a call for help

Underneath BuildConsole which I assume is a wrapper to prepare an internal
build request likely calls Devenv or MSBuild. Both are available in Pro and
CE. Express only has MSBuild.

Building from a blank build-vc120 with Devenv provides a significant build
time improvement over MSBuild. However, a note on MS's web page for Denenv
indicate that MSBuild should be used. That note has been present since
VS2010 release. My thoughts are that the note was there with aim of easing
the transition for C# and .NET developers that had historically used
MSBuild into C++.

One additional point. Singularity Viewer project still uses develop.py and
it internally calls devenv.com with no bad result, as far as I know.

For the list:
Should autobuild.xml call MSBuild or Devenv?

On Wed, Feb 4, 2015 at 8:18 AM, Oz Linden (Scott Lawrence)  wrote:

>  On 2015-02-02 10:42 , Nicky Perian wrote:
>
>
>  Does the underlying builder in LL's automated build system call MSBuild
> or Devenv?
>
>
> Neither - as you can see in the autobuild.xml configuration, it runs
> 'BuildConsole'.
>
> I don't see any value at all in maintaining compatibility with Express
> given that the Community Edition is closer to the Pro version we use; if
> anyone disagrees, by all means make your case but "because we used to do it
> that way" isn't going to be a strong argument.
>
> I'm pretty tied up in an internal planning conference this week (figuring
> out good things to do for Second Life in the coming several months), so
> please forgive me if my responses are even slower than usual.
>
> --
>  *Oz Linden (Scott Lawrence)* | *Engineering Director, Second Life*
> Email or Hangouts o...@lindenlab.com | Second Life Oz 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] Viewer Tools Upgrades - with a call for help

2015-02-04 Thread Oz Linden (Scott Lawrence)


On 2015-02-02 10:42 , Nicky Perian wrote:


Does the underlying builder in LL's automated build system call 
MSBuild or Devenv?




Neither - as you can see in the autobuild.xml configuration, it runs 
'BuildConsole'.


I don't see any value at all in maintaining compatibility with Express 
given that the Community Edition is closer to the Pro version we use; if 
anyone disagrees, by all means make your case but "because we used to do 
it that way" isn't going to be a strong argument.


I'm pretty tied up in an internal planning conference this week 
(figuring out good things to do for Second Life in the coming several 
months), so please forgive me if my responses are even slower than usual.


--
*Oz Linden (Scott Lawrence)* | /Engineering Director, Second Life/
Email or Hangouts o...@lindenlab.com  | Second 
Life Oz 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] Viewer Tools Upgrades - with a call for help

2015-02-02 Thread Nicky Perian

I am asking because when we went through the change for 2005->2010 (see
issue OPEN-1) LL used devenv in their systems and several of their dev's
had autobuild on personal dev boxes that pointed to devenv. The problem was
that many of the OS developers,  would be contributors, were using VS2010
Express and it did not have devenv so, the option chosen was to use MSBuild
for opensource and continue use of devenv at LL. This provided a
satisfactory solution which has served us well. But, all along their was
lurking about the fact that the 2 build systems did not match. So, when I
saw that VS2013 CE had devenv I wanted to test it. Granted the MS note to
use the improved build program MSBuild was present on MS's web page at
VS2010 launch. However, at that time LL continued to use Devenv. Things
change over time and it could be that LL has updated their automated build
scripts to favor MSBuild.
Thus, the question is: "Does the underlying builder in LL's automated build
system call MSBuild or Devenv?"

On Mon, Feb 2, 2015 at 1:00 PM, Cinder Roxley 
wrote:

> On February 2, 2015 at 11:42:10 AM, Nicky Perian (nickyper...@gmail.com)
> wrote:
>
>
> Does the underlying builder in LL's automated build system call MSBuild or
> Devenv?
>
>
> If it’s Team City or Bamboo, then it calls MSBuild like Microsoft
> recommends. Not sure about others. Drake has fixed the issue with command
> line building using msbuild and we posted a link in the relevant jira. The
> fix is much simpler and doesn’t create additional build targets.
> https://bitbucket.org/LightDrake/open-290/commits/a3716dfdd1f6da9d91b5b708f7f372101e24d572
> --
> Cinder Roxley
> Sent with Airmail
>
>
>
> On Mon, Feb 2, 2015 at 12:30 PM, Oz Linden (Scott Lawrence) <
> o...@lindenlab.com> wrote:
>
>> On 2015-01-31 11:41 , Nicky Perian wrote:
>>
>> Two  methods for command line building have been tested each starting
>> with a fresh build-vc120 directory, with tests and package on.
>> Machine spec is Intel i7 all 8 cores running with 6GB memory.
>>
>> autobuild configure -c ReleaseOSCE and autobuild build -c ReleaseOSCE
>> Calls Devenv.exe which is the build program for VS2013 Community Edition
>> Build completed in 53 minutes.
>>
>> autobuild configure -c ReleaseOS and autobuild build -c ReleaseOS
>> Calls MSBuild.exe which is the build program available in VS2013 Express
>> Edition AND VS2013 Community Edition.
>> Build completes in 77 minutes.
>>
>> Should we provide open source developers both methods?
>>
>>
>> I would prefer not to support more than one configuration for internal
>> use and one for external use.
>>
>>
>
> ___
> 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] Viewer Tools Upgrades - with a call for help

2015-02-02 Thread Cinder Roxley

On February 2, 2015 at 11:42:10 AM, Nicky Perian (nickyper...@gmail.com) wrote:

Does the underlying builder in LL's automated build system call MSBuild or
Devenv?

If it’s Team City or Bamboo, then it calls MSBuild like Microsoft recommends.
Not sure about others. Drake has fixed the issue with command line building
using msbuild and we posted a link in the relevant jira. The fix is much
simpler and doesn’t create additional build targets.
https://bitbucket.org/LightDrake/open-290/commits/a3716dfdd1f6da9d91b5b708f7f372101e24d572

--
Cinder Roxley
Sent with Airmail

On Mon, Feb 2, 2015 at 12:30 PM, Oz Linden (Scott Lawrence)
wrote:
On 2015-01-31 11:41 , Nicky Perian wrote:
Two methods for command line building have been tested each starting with a
fresh build-vc120 directory, with tests and package on.
Machine spec is Intel i7 all 8 cores running with 6GB memory.

autobuild configure -c ReleaseOSCE and autobuild build -c ReleaseOSCE
Calls Devenv.exe which is the build program for VS2013 Community Edition
Build completed in 53 minutes.

autobuild configure -c ReleaseOS and autobuild build -c ReleaseOS
Calls MSBuild.exe which is the build program available in VS2013 Express
Edition AND VS2013 Community Edition.
Build completes in 77 minutes.

Should we provide open source developers both methods?

I would prefer not to support more than one configuration for internal use and
one for external use.

___
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] Viewer Tools Upgrades - with a call for help

2015-02-02 Thread Nicky Perian

Does the underlying builder in LL's automated build system call MSBuild or
Devenv?

On Mon, Feb 2, 2015 at 12:30 PM, Oz Linden (Scott Lawrence) <
o...@lindenlab.com> wrote:

>  On 2015-01-31 11:41 , Nicky Perian wrote:
>
>  Two  methods for command line building have been tested each starting
> with a fresh build-vc120 directory, with tests and package on.
> Machine spec is Intel i7 all 8 cores running with 6GB memory.
>
>  autobuild configure -c ReleaseOSCE and autobuild build -c ReleaseOSCE
> Calls Devenv.exe which is the build program for VS2013 Community Edition
> Build completed in 53 minutes.
>
>  autobuild configure -c ReleaseOS and autobuild build -c ReleaseOS
> Calls MSBuild.exe which is the build program available in VS2013 Express
> Edition AND VS2013 Community Edition.
> Build completes in 77 minutes.
>
>  Should we provide open source developers both methods?
>
>
> I would prefer not to support more than one configuration for internal use
> and one for external use.
>
>
> --
>  *Oz Linden (Scott Lawrence)* | *Engineering Director, Second Life*
> Email or Hangouts o...@lindenlab.com | Second Life Oz 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
>
___
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] Viewer Tools Upgrades - with a call for help

2015-02-02 Thread Oz Linden (Scott Lawrence)


On 2015-01-31 11:41 , Nicky Perian wrote:
Two  methods for command line building have been tested each starting 
with a fresh build-vc120 directory, with tests and package on.

Machine spec is Intel i7 all 8 cores running with 6GB memory.

autobuild configure -c ReleaseOSCE and autobuild build -c ReleaseOSCE
Calls Devenv.exe which is the build program for VS2013 Community Edition
Build completed in 53 minutes.

autobuild configure -c ReleaseOS and autobuild build -c ReleaseOS
Calls MSBuild.exe which is the build program available in VS2013 
Express Edition AND VS2013 Community Edition.

Build completes in 77 minutes.

Should we provide open source developers both methods?



I would prefer not to support more than one configuration for internal 
use and one for external use.



--
*Oz Linden (Scott Lawrence)* | /Engineering Director, Second Life/
Email or Hangouts o...@lindenlab.com  | Second 
Life Oz 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] Viewer Tools Upgrades - with a call for help

2015-02-02 Thread Oz Linden (Scott Lawrence)


On 2015-01-31 17:38 , Nicky Perian wrote:

Anyone know what causes this on a release build?
Doesn't stop the build and the installer is still made.
3>-- Build started: Project: generate_viewer_version, 
Configuration: Release Win32 --

3>  processing
3>  'printf' is not recognized as an internal or external command,
3>  operable program or batch file.
3>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5): 
error MSB6006: "cmd.exe" exited with code 9009.


Appears to come from newview/CMakeLists.txt
source_group("CMake Rules" FILES ViewerInstall.cmake)

# the viewer_version.txt file created here is for passing to 
viewer_manifest and autobuild
# the summary.json file is created for the benefit of the TeamCity 
builds, where

# it is used to provide descriptive information to the build results page
add_custom_target(generate_viewer_version ALL
  COMMAND printf 
'${VIEWER_SHORT_VERSION}.${VIEWER_VERSION_REVISION}' > 
${CMAKE_CURRENT_BINARY_DIR}/viewer_version.txt
  COMMAND printf 
'{"Type":"viewer","Version":"${VIEWER_SHORT_VERSION}.${VIEWER_VERSION_REVISION}"}' 
> ${CMAKE_BINARY_DIR}/summary.json
  COMMENT Generating viewer_version.txt for manifest 
processing

  )


That looks like cmake is trying to run commands in a windows shell 
rather than bash; the printf is a bash command.  This works in our build 
environment. It's possible that it could be replaced with cmake FILE 
commands?


--
*Oz Linden (Scott Lawrence)* | /Engineering Director, Second Life/
Email or Hangouts o...@lindenlab.com  | Second 
Life Oz 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] Viewer Tools Upgrades - with a call for help

2015-02-02 Thread Jonathan Ballard

What did not work in production is compression and encryption with, said,
"foreign agendas," inefficiencies, power consumption. In game mechanics,
those tests are ignored and seem irrelevant because it is working. Under
applied STEM research, even openjpeg failed production factors. If it
doesn't work nicely (on bare metal) then it is subject for *external* video
card mechanics and those agendas, warranties.

We have not received any digitally signed TOS tokens that specifically
enable *Auto*build or register certain build features. The challenge is
there, as the lawyers said, "it doesn't benefit me."

In California, ibid.

On Fri, Jan 30, 2015 at 1:41 PM, Oz Linden (Scott Lawrence) <
o...@lindenlab.com> wrote:

>  On 2015-01-30 11:51 , Tank Master wrote:
>
> You are getting an error because that isn't a valid command.  Use
> "autobuild configure -c RelWithDebInfoOS" OR "autobuild configure -c
> ReleaseOS"  Also, This will still fail do to tests.  I used: "autobuild
> configure -c ReleaseOS -- -DPACKAGE:BOOL=OFF -DLL_TESTS:BOOL=OFF" to turn
> off both packaging and tests.
>
>
> The tests should work - they do for us, though I suppose some may depend
> on libs not in open source.
>
> --
>  *Oz Linden (Scott Lawrence)* | *Engineering Director, Second Life*
> Email or Hangouts o...@lindenlab.com | Second Life Oz 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
>
___
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] Viewer Tools Upgrades - with a call for help

2015-02-01 Thread Wolfpup Lowenhar

Hello everyone,

   It has been a long time since the last time I have worked on the viewer and 
when I saw about the tool chain upgrade to use VS2013 I started working on it.

Now to the issues concerning FModEX, QuickTime,  and Havok.

First FModEX : there is a switch already present for adding FModEX to the OS 
Builds all you have to do is add -DFMODEX:BOOL=ON to the autobuild.xml file in 
the proper OS build settings. Also it looks like there needs to be an 
additional switch added to use the FModEX libs if you have it installed in your 
system because when I did a test build using the local package that I have the 
package is marked as 'dirty' since there is no metadata in the package.

Second QuickTime: First the Quicktime.cmake file has to be modified to add 
switches -DUSE_QUICKTIME:BOOL=TRUE and -DUSE_QUICKTIME_LOCAL_REPO:BOOL=TRUE so 
that the OS community can use their local installation of the QuickTime SDK 
with one file in the SDK modified so that it does not collide with the windows 
system files during the build as per the noted modifications in the previous 
windows build setup instructions. I am getting an error during the 
configuration process and am wondering if it is the newer version of cmake not 
accepting the mods I have made to the cmake file.

Here is a diff of the change I have made:

@@ -1,7 +1,7 @@

# -*- cmake -*-

-if(INSTALL_PROPRIETARY)

+if(USE_QUICKTIME)

   include(Prebuilt)

   if (WINDOWS)

 use_prebuilt_binary(quicktime)

   endif (WINDOWS)

@@ -4,10 +4,10 @@

   include(Prebuilt)

   if (WINDOWS)

 use_prebuilt_binary(quicktime)

   endif (WINDOWS)

-endif(INSTALL_PROPRIETARY)

+endif(USE_QUICKTIME)

 if (DARWIN)

   include(CMakeFindFrameworks)

   find_library(QUICKTIME_LIBRARY QuickTime)

elseif (WINDOWS)

@@ -9,10 +9,15 @@

 if (DARWIN)

   include(CMakeFindFrameworks)

   find_library(QUICKTIME_LIBRARY QuickTime)

elseif (WINDOWS)

-  set(QUICKTIME_SDK_DIR "$ENV{PROGRAMFILES}/QuickTime SDK"

-  CACHE PATH "Location of the QuickTime SDK.")

+if (USE_QUICKTIME_LOCAL_REPO)

+set(QUICKTIME_SDK_DIR "$ENV(QUICKTIME_SDK_DIR)"

+CACHE PATH "Location of the QuickTime SDK.")

+else (APPLE LOCAL SDK)

+set(QUICKTIME_SDK_DIR "$ENV{PROGRAMFILES}/QuickTime SDK"

+CACHE PATH "Location of the QuickTime SDK.")

+endif (USE_QUICKTIME_LOCAL_REPO)

   find_library(DEBUG_QUICKTIME_LIBRARY qtmlclient.lib

PATHS

I'm getting the error on the two variables USE_QUICKTIME and 
USE_QUICKTIME_LOCAL_REPO now these work just fine in the VS2010 builds with 
Cmake 2.8 so I'm wondering if it is a change in Cmake that might be causing the 
issue. The error that is being thrown is about the variables not being use and 
ignored so it does not affect the configure or the build. I will continue to 
work on this and see if I can correct this issue once I have it worked out I 
will post a jira issue and include a working repo based off the needed changes 
for going through the needed steps for approval for including in the viewer 
source.

Third Havok is a proprietary third party lib that has to be bought in order for 
anyone in the OS community to use it now there are some TPV's that use and Open 
Source system that is similar so that those viewers have mesh functionality. On 
this I had work on some myself in the past as an Open Source option that LL 
could provide to the OS community even though that did not progress very far.

From: opensource-dev-boun...@lists.secondlife.com 
[mailto:opensource-dev-boun...@lists.secondlife.com] On Behalf Of Callum 
Prentice (Callum)
Sent: Thursday, January 29, 2015 5:06 PM
To: Henri Beauchamp
Cc: opensource-dev
Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help

Yep - we need to add the right set of parameters to 'autobuild' to set up FMod, 
Havok QuickTime etc.

Can anyone tell me what they are or point me at the right doc before I start 
searching.

On Thu, Jan 29, 2015 at 12:44 PM, Henri Beauchamp  wrote:

On Thu, 29 Jan 2015 11:45:46 +0100, Henri Beauchamp wrote:

> On Wed, 28 Jan 2015 10:53:11 -0500, Oz Linden (Scott Lawrence) wrote:
>
> > We've also put up a new page of instructions on how to set up a Windows
> > development environment
> > <https://wiki.secondlife.com/wiki/Visual_Studio_2013_Viewer_Builds>.
> > Suggestions for improvement are most welcome here and on the Talk
> > page... we're trying to keep it as simple as possible while being
> > sufficient to build a clean checkout of the viewer.
>
> Missing bits:
>
> - When using Windows 7, you must also update from IE8 to a newer version
> since else, you can't log in to register for a free license from within
> Visual Studio 2013 Community (the IE8 Javascript engine fails on two of
> the scripts u

Re: [opensource-dev] Viewer Tools Upgrades - with a call for help

2015-02-01 Thread Jonathan Welch

Dropping in Tank's modified cmake file was not successful for me.
During the configure step there were errors and the final result did
not produce a .sln file.  So I will wait until his patch is officially
incorporated before testing these instructions further.

On Sun, Feb 1, 2015 at 8:48 AM, Jonathan Welch  wrote:
> More notes:
> The Tortoise HG link points to the main web page, not to the file we
> are supposed to download.
>
> The CMake link points to the main web page, not to the file we are
> supposed to download.
> Also, the instructions call for version 3.1.0.  The latest version is
> 3.1.1 and the version just prior to that one is 3.0.2.
>
> Same issue for Cygwin link pointing to main web page.
>
> Intermediate check -- instructions needed on how to open a cygwin
> terminal.  Inconsistent word usage; previously it was called a shell.
>
> Even better would be to only use the command prompt window.  Less
> confusing than having to remember what window to do various operations
> in.
>
> In Install Autobuild there is a clickable link that should not be there:
> http://bitbucket.org/oz_linden/autobuild-metadata#egg=autobuild
>
> In Update system PATH instructions on how to proceed in the Control
> Panel are needed.
>
> Oups, I have to go and apply Tank's patch for DirectX, as that has not
> made it into the instructions yet.
___
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] Viewer Tools Upgrades - with a call for help

2015-02-01 Thread Jonathan Welch

More notes:
The Tortoise HG link points to the main web page, not to the file we
are supposed to download.

The CMake link points to the main web page, not to the file we are
supposed to download.
Also, the instructions call for version 3.1.0.  The latest version is
3.1.1 and the version just prior to that one is 3.0.2.

Same issue for Cygwin link pointing to main web page.

Intermediate check -- instructions needed on how to open a cygwin
terminal.  Inconsistent word usage; previously it was called a shell.

Even better would be to only use the command prompt window.  Less
confusing than having to remember what window to do various operations
in.

In Install Autobuild there is a clickable link that should not be there:
http://bitbucket.org/oz_linden/autobuild-metadata#egg=autobuild

In Update system PATH instructions on how to proceed in the Control
Panel are needed.

Oups, I have to go and apply Tank's patch for DirectX, as that has not
made it into the instructions yet.
___
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] Viewer Tools Upgrades - with a call for help

2015-01-31 Thread Nicky Perian

Anyone know what causes this on a release build?Doesn't stop the build and the 
installer is still made.3>-- Build started: Project: 
generate_viewer_version, Configuration: Release Win32 --
3>  processing3>  'printf' is not recognized as an internal or external 
command,3>  operable program or batch file.3>C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets(170,5): error 
MSB6006: "cmd.exe" exited with code 9009.
Appears to come from newview/CMakeLists.txtsource_group("CMake Rules" FILES 
ViewerInstall.cmake)
# the viewer_version.txt file created here is for passing to viewer_manifest 
and autobuild# the summary.json file is created for the benefit of the TeamCity 
builds, where#   it is used to provide descriptive information to the build 
results pageadd_custom_target(generate_viewer_version ALL                  
COMMAND printf '${VIEWER_SHORT_VERSION}.${VIEWER_VERSION_REVISION}' > 
${CMAKE_CURRENT_BINARY_DIR}/viewer_version.txt                  COMMAND printf 
'{"Type":"viewer","Version":"${VIEWER_SHORT_VERSION}.${VIEWER_VERSION_REVISION}"}'
 > ${CMAKE_BINARY_DIR}/summary.json                  COMMENT Generating 
viewer_version.txt for manifest processing                  )


 
  From: Oz Linden (Scott Lawrence) 
 To: opensource-dev  
 Sent: Wednesday, January 28, 2015 9:53 AM
 Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help
   
  On 2014-12-23 18:17 , Oz Linden (Scott Lawrence) wrote:
  
 
 As some of you are certainly aware, the Linden viewer devs have been busy for 
the last several weeks updating our tools for building viewers. The tools 
changes include:

   - Windows building with Visual Studio 2013   
 
   - Mac building on OSX 10.10 with Xcode 6.1
   - Linux building with gcc 4.6
   - All platforms using Autobuild 1.0
 The canonical repository for this is 
https://bitbucket.org/lindenlab/viewer-tools-update , and the various packages 
each have a lindenlab/3p-update-name repository (those will be pulled to the 
3p-name repos when the viewer that uses them is promoted to viewer-release).
 
 
 Just a quick update... we are now into the QA phase with this, and there is a 
Project Viewer available on the Alternate Viewers page (there is a known issue 
with the Windows installer that I believe affects anyone that does not have 
developer tools installed... a fix should be out very shortly).
 
 We've also put up a new page of instructions on how to set up a Windows 
development environment.  Suggestions for improvement are most welcome here and 
on the Talk page... we're trying to keep it as simple as possible while being 
sufficient to build a clean checkout of the viewer.
 
 -- 
  Oz Linden (Scott Lawrence) | Engineering Director, Second Life
 Email or Hangouts o...@lindenlab.com | Second Life Oz 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

   
___
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] Viewer Tools Upgrades - with a call for help

2015-01-31 Thread Jonathan Ballard

*Sounds like a job...*

I have not played games.

Compiled like amazing grace.


PS. Initially, I'd like us to focus on getting the current functionality
> working.
>
> -- 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] Viewer Tools Upgrades - with a call for help

2015-01-31 Thread Cinder Roxley

Hi,

I thought the plan was to only support VS2013 Community Edition and support for 
Express since Community Edition is, for all intents and purposes, free and 
without any further restrictions than the LGPL already lays out? There’s really 
absolutely no reason for using Express since all qualifications are met for 
both individuals and organizations building the viewer because the source code 
has already been released under an OSI-approved license that we all must adhere 
to anyways.

In short, why support both methods when one is vastly superior with no 
disadvantages?

-- 
Cinder Roxley
Sent with Airmail

On January 31, 2015 at 9:39:44 AM, Nicky Perian (nickyper...@yahoo.com) wrote:

[#OPEN-290] Windows Toolchain update - Second Life Bug Tracker
 
 
 
 
 
 
[#OPEN-290] Windows Toolchain update - Second Life Bug Tracker
Document and offer patches for Windows Platform open source building.
View on jira.secondlife.com
Preview by Yahoo
 
Two  methods for command line building have been tested each starting with a 
fresh build-vc120 directory, with tests and package on.
Machine spec is Intel i7 all 8 cores running with 6GB memory.

autobuild configure -c ReleaseOSCE and autobuild build -c ReleaseOSCE
Calls Devenv.exe which is the build program for VS2013 Community Edition
Build completed in 53 minutes.

autobuild configure -c ReleaseOS and autobuild build -c ReleaseOS
Calls MSBuild.exe which is the build program available in VS2013 Express 
Edition AND VS2013 Community Edition.
Build completes in 77 minutes.

Should we provide open source developers both methods?

Patch is here:

NickyP / viewer-tools-update-OPEN-290 / commit / 96461e3be52e — Bitbucket
 
 
 
 
 
 
NickyP / viewer-tools-update-OPEN-290 / commit / 96461e3be52e — Bitbucket
name RelWithDebInfoOS
View on bitbucket.org
Preview by Yahoo
 



From: Oz Linden (Scott Lawrence) 
To: opensource-dev@lists.secondlife.com
Sent: Friday, January 30, 2015 3:41 PM
Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help



On 2015-01-30 11:51 , Tank Master wrote:
You are getting an error because that isn't a valid command.  Use "autobuild 
configure -c RelWithDebInfoOS" OR "autobuild configure -c ReleaseOS"  Also, 
This will still fail do to tests.  I used: "autobuild configure -c ReleaseOS -- 
-DPACKAGE:BOOL=OFF -DLL_TESTS:BOOL=OFF" to turn off both packaging and tests.


The tests should work - they do for us, though I suppose some may depend on 
libs not in open source.

--
Oz Linden (Scott Lawrence) | Engineering Director, Second Life
Email or Hangouts o...@lindenlab.com | Second Life Oz 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


___  
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] Viewer Tools Upgrades - with a call for help

2015-01-31 Thread Nicky Perian

[#OPEN-290] Windows Toolchain update - Second Life Bug Tracker
|   |
|   |   |   |   |   |
| [#OPEN-290] Windows Toolchain update - Second Life Bug TrackerDocument and 
offer patches for Windows Platform open source building.  |
|  |
| View on jira.secondlife.com | Preview by Yahoo |
|  |
|   |

Two  methods for command line building have been tested each starting with a 
fresh build-vc120 directory, with tests and package on.Machine spec is Intel i7 
all 8 cores running with 6GB memory.

autobuild configure -c ReleaseOSCE and autobuild build -c ReleaseOSCECalls 
Devenv.exe which is the build program for VS2013 Community EditionBuild 
completed in 53 minutes.
autobuild configure -c ReleaseOS and autobuild build -c ReleaseOSCalls 
MSBuild.exe which is the build program available in VS2013 Express Edition AND 
VS2013 Community Edition.Build completes in 77 minutes.
Should we provide open source developers both methods?
Patch is here:
NickyP / viewer-tools-update-OPEN-290 / commit / 96461e3be52e — Bitbucket

|   |
|   |   |   |   |   |
| NickyP / viewer-tools-update-OPEN-290 / commit / 96461e3be52e — 
Bitbucketname RelWithDebInfoOS  |
|  |
| View on bitbucket.org | Preview by Yahoo |
|  |
|   |




 
  From: Oz Linden (Scott Lawrence) 
 To: opensource-dev@lists.secondlife.com 
 Sent: Friday, January 30, 2015 3:41 PM
 Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help
   
 

On 2015-01-30 11:51 , Tank Master wrote:
  
 #yiv4793376836 #yiv4793376836 --.yiv4793376836hmmessage 
P{margin:0px;padding:0px;}#yiv4793376836 
body.yiv4793376836hmmessage{font-size:12pt;font-family:Calibri;}#yiv4793376836  
You are getting an error because that isn't a valid command.  Use "autobuild 
configure -c RelWithDebInfoOS" OR "autobuild configure -c ReleaseOS"  Also, 
This will still fail do to tests.  I used: "autobuild configure -c ReleaseOS -- 
-DPACKAGE:BOOL=OFF -DLL_TESTS:BOOL=OFF" to turn off both packaging and tests.
  
 
 The tests should work - they do for us, though I suppose some may depend on 
libs not in open source.
 
 -- 
  Oz Linden (Scott Lawrence) | Engineering Director, Second Life
 Email or Hangouts o...@lindenlab.com | Second Life Oz 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

   
___
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] Viewer Tools Upgrades - with a call for help

2015-01-30 Thread Cinder Roxley

Hi,

All the tests pass for me using the open source build. If they aren’t passing 
it would be good to file a jira or post the failures here so they can be fixed.

-- 
Cinder Roxley
Sent with Airmail

On January 30, 2015 at 2:41:09 PM, Oz Linden (Scott Lawrence) 
(o...@lindenlab.com) wrote:

On 2015-01-30 11:51 , Tank Master wrote:
You are getting an error because that isn't a valid command.  Use "autobuild 
configure -c RelWithDebInfoOS" OR "autobuild configure -c ReleaseOS"  Also, 
This will still fail do to tests.  I used: "autobuild configure -c ReleaseOS -- 
-DPACKAGE:BOOL=OFF -DLL_TESTS:BOOL=OFF" to turn off both packaging and tests.

The tests should work - they do for us, though I suppose some may depend on 
libs not in open source.

--
Oz Linden (Scott Lawrence) | Engineering Director, Second Life
Email or Hangouts o...@lindenlab.com | Second Life Oz 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___
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] Viewer Tools Upgrades - with a call for help

2015-01-30 Thread Oz Linden (Scott Lawrence)


On 2015-01-30 11:51 , Tank Master wrote:
You are getting an error because that isn't a valid command.  Use 
"autobuild configure -c RelWithDebInfoOS" OR "autobuild configure -c 
ReleaseOS"  Also, This will still fail do to tests.  I used: 
"autobuild configure -c ReleaseOS -- -DPACKAGE:BOOL=OFF 
-DLL_TESTS:BOOL=OFF" to turn off both packaging and tests.


The tests should work - they do for us, though I suppose some may depend 
on libs not in open source.


--
*Oz Linden (Scott Lawrence)* | /Engineering Director, Second Life/
Email or Hangouts o...@lindenlab.com  | Second 
Life Oz 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] Viewer Tools Upgrades - with a call for help

2015-01-30 Thread Nicky Perian


Command line building:1. Add to path:--> C:\Program Files 
(x86)\MSBuild\12.0\Bin  note: case matters.2. In cygwin64 terminal  cd into 
viewer-tools-update
3. execute -->  msbuild build-vc120/secondlife.sln /t:Build /p:4. 
With buildtype being Release or RelWithDebInfo
This should work with autobuild build -c RelWithDebInfoOSBut, alas new 
autobuild is path challenged.  In work:1. make it work with autobuild2. ...
... Change build options in autobuild.xml as below and with the above change to 
PATH autobuild build -c RelWithDebInfo works correctly.
Since the community edition is available we may want to use Devenv and adjust 
the options to match callsto it. But, that would still not be an exact match to 
LL because LL's of use of automatic build tools.
Boils down to this works lets leave it alone or, do we want to try Devenv 
command line build?





            RelWithDebInfoOS                          
build                              arguments         
                         SecondLife.sln                
                command                
msbuild.exe                options                
                  /t:Build                  
/p:PlatformToolset=v120                  
/p:Configuration=RelWithDebInfo                  
/p:Platform=Win32                              
 
   

   From: Oz Linden (Scott Lawrence) 
 To: opensource-dev@lists.secondlife.com 
 Sent: Thursday, January 29, 2015 6:04 PM
 Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help
   
 On 2015-01-28 19:23 , Callum Prentice (Callum) wrote:
  
  I can try it on an XP system tomorrow when I'm in the office and have access 
to the QA Lab.  
 
 
 To be clear... XP is not supported and if it does not work, that is not a bug.
 
 If it does happen to work, I don't object, but we won't spend time on it if it 
doesn't.
 
 We announced that we'd dropped XP support several months ago.  
 
 -- 
  Oz Linden (Scott Lawrence) | Engineering Director, Second Life
 Email or Hangouts o...@lindenlab.com | Second Life Oz 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

   
___
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] Viewer Tools Upgrades - with a call for help

2015-01-30 Thread Melissa Browne

Hi Tank, I found that the download of files became corrupted. By reloading the 
cloned files and using your suggestion it built just fine thanks. I do suggest 
that someone modify the misleading line “autobuild configure -c 
RelWithDebInfoOS|ReleaseOS” that will corrupt the download when ran. One has to 
guess if the author meant to use | as part of the command line or the word or. 
Guessing wrong requires starting over...just pointing it out. 
MB___
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] Viewer Tools Upgrades - with a call for help

2015-01-30 Thread Tank Master

On the other hand, we should still find out so we can modify the installer to 
explicitly block the install on XP or any other setup that won't run the new 
code (such as possibly Vista with no SP) if testing determines the viewer wont 
actually run on those platforms.~TM

Date: Thu, 29 Jan 2015 19:04:01 -0500
From: o...@lindenlab.com
To: opensource-dev@lists.secondlife.com
Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help


  

  
  
On 2015-01-28 19:23 , Callum Prentice
  (Callum) wrote:



  
I can try it on an XP
  system tomorrow when I'm in the office and have access to the
  QA Lab.
  
  




To be clear... XP is not supported and if it does not work, that is
not a bug.



If it does happen to work, I don't object, but we won't spend time
on it if it doesn't.



We announced that we'd dropped XP support several months ago.  



-- 

  
Oz Linden (Scott Lawrence) | Engineering Director,
  Second Life

Email or
  Hangouts o...@lindenlab.com | Second Life Oz 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  
  ___
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] Viewer Tools Upgrades - with a call for help

2015-01-30 Thread Tank Master

You are getting an error because that isn't a valid command.  Use "autobuild 
configure -c RelWithDebInfoOS" OR "autobuild configure -c ReleaseOS"  Also, 
This will still fail do to tests.  I used: "autobuild configure -c ReleaseOS -- 
-DPACKAGE:BOOL=OFF -DLL_TESTS:BOOL=OFF" to turn off both packaging and tests.
~TM
From: moonbots...@centurylink.net
To: opensource-dev@lists.secondlife.com
Date: Fri, 30 Jan 2015 10:43:22 -0600
Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help




Can anyone 
point what the autobuild error “ERROR: default configuration returned 1” means 
when running the “autobuild configure -c RelWithDebInfoOS|ReleaseOS” 
command?

___
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] Viewer Tools Upgrades - with a call for help

2015-01-30 Thread Melissa Browne

Can anyone point what the autobuild error “ERROR: default configuration 
returned 1” means when running the “autobuild configure -c 
RelWithDebInfoOS|ReleaseOS” command?___
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] Viewer Tools Upgrades - with a call for help

2015-01-30 Thread Nicky Perian

Command line building:1. Add to path:--> C:\Program Files 
(x86)\MSBuild\12.0\Bin  note: case matters.2. In cygwin64 terminal  cd into 
viewer-tools-update
3. execute -->  msbuild build-vc120/secondlife.sln /t:Build /p: 4. 
With buildtype being Release or RelWithDebInfo
This should work with autobuild build -c RelWithDebInfoOSBut, alas new 
autobuild is path challenged.  In work:1. make it work with autobuild2. ...

 On Friday, January 30, 2015 3:26 AM, Henri Beauchamp  wrote:

 On Thu, 29 Jan 2015 14:06:17 -0800, Callum Prentice (Callum) wrote:

> Yep - we need to add the right set of parameters to 'autobuild' to set
> up FMod, Havok QuickTime etc.
> 
> Can anyone tell me what they are or point me at the right doc before I
> start searching.

I can't help you about the autobuild system itself, because I only build
the Cool VL Viewer (v1 UI viewer with v2/3 code I backported to it), and
it doesn't use autobuild at all...

When building it, I first run a winprebuild.bat batch script that I wrote
and that simply takes care of copying the FMOD Ex files in the viewer
sources tree lib/ and include/ (and newview/, for the dll itself)
directories. Here is the relevant part of the batch script:

rem Copy of the fmod headers and libs:
set FMOD_DIR="C:\Program Files\FMOD SoundSystem\FMOD Programmers API Windows"
xcopy /y %FMOD_DIR%\api\inc\* ..\include\
copy /y %FMOD_DIR%\api\lib\fmodex_vc.lib ..\lib\release\
copy /y %FMOD_DIR%\api\lib\fmodexL_vc.lib ..\lib\debug\
copy /y %FMOD_DIR%\api\fmodex.dll newview\

The FMOD Ex package for Windows can be found here:
http://www.fmod.org/download/fmodex/api/Win/fmodapiNwin-installer.exe
where N is the version number (44450 as I'm writing this) and the
download page with up to date links to the files is:
http://www.fmod.org/download-previous-products/ (notice the "previous"...
It means that FMOD Ex is going to be phased out... Any plan from LL to
replace it in future viewers ?).

For Quictime, VS2010 (I didn't yet try with VS2013) and cmake do find
the SDK by themselves (so there's no need to copy the libraries and
include files like needed with FMOD Ex).

I don't have a ready-made URL for the Quicktime SDK (the TPV builder
will have to register an Apple's devel account, log in and dig into
their site to find the old Quicktime v7.3 SDK... It'd be about time
LL would find a way to get media working under Windows without having
to use that (long) deprecated Quicktime SDK...).

As for Havok, not all TPVs can use it (obviously, genuine (L)GPL TPVs
can't)... I'm using HACD to replace the Havok library for mesh
decompositions, and I simply don't have the pathfinding "capsule and
path" rendering tool implemented.

Regards,

Henri.
___
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] Viewer Tools Upgrades - with a call for help

2015-01-30 Thread Henri Beauchamp

On Thu, 29 Jan 2015 14:06:17 -0800, Callum Prentice (Callum) wrote:

> Yep - we need to add the right set of parameters to 'autobuild' to set
> up FMod, Havok QuickTime etc.
> 
> Can anyone tell me what they are or point me at the right doc before I
> start searching.

I can't help you about the autobuild system itself, because I only build
the Cool VL Viewer (v1 UI viewer with v2/3 code I backported to it), and
it doesn't use autobuild at all...

When building it, I first run a winprebuild.bat batch script that I wrote
and that simply takes care of copying the FMOD Ex files in the viewer
sources tree lib/ and include/ (and newview/, for the dll itself)
directories. Here is the relevant part of the batch script:

rem Copy of the fmod headers and libs:
set FMOD_DIR="C:\Program Files\FMOD SoundSystem\FMOD Programmers API Windows"
xcopy /y %FMOD_DIR%\api\inc\* ..\include\
copy /y %FMOD_DIR%\api\lib\fmodex_vc.lib ..\lib\release\
copy /y %FMOD_DIR%\api\lib\fmodexL_vc.lib ..\lib\debug\
copy /y %FMOD_DIR%\api\fmodex.dll newview\

The FMOD Ex package for Windows can be found here:
http://www.fmod.org/download/fmodex/api/Win/fmodapiNwin-installer.exe
where N is the version number (44450 as I'm writing this) and the
download page with up to date links to the files is:
http://www.fmod.org/download-previous-products/ (notice the "previous"...
It means that FMOD Ex is going to be phased out... Any plan from LL to
replace it in future viewers ?).

For Quictime, VS2010 (I didn't yet try with VS2013) and cmake do find
the SDK by themselves (so there's no need to copy the libraries and
include files like needed with FMOD Ex).

I don't have a ready-made URL for the Quicktime SDK (the TPV builder
will have to register an Apple's devel account, log in and dig into
their site to find the old Quicktime v7.3 SDK... It'd be about time
LL would find a way to get media working under Windows without having
to use that (long) deprecated Quicktime SDK...).

As for Havok, not all TPVs can use it (obviously, genuine (L)GPL TPVs
can't)... I'm using HACD to replace the Havok library for mesh
decompositions, and I simply don't have the pathfinding "capsule and
path" rendering tool implemented.

Regards,

Henri.
___
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] Viewer Tools Upgrades - with a call for help

2015-01-29 Thread Nicky Perian

On my system I had installed vs2013 Express before installing the community 
edition.The file extension *.sln was set to run Express.From "cygstart 
build-vc120/secondlife.sln" Express builds and runs the resulting viewer 
without error.
If I open either Community or Express from the  Desktop Icon the build errors 
out with:
.Error 1 error MSB6006: "cmd.exe" exited with code 9009. C:\Program Files 
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppCommon.targets 170 5 
generate_viewer_version
 

 On Thursday, January 29, 2015 7:57 PM, Nicky Perian 
 wrote:
   
 

 It does not run on XP.  The error is that it is nor a valid windows 32 bit 
application.
That brings up another question. Will it run on 32 bit variants of vista and 
win7? 

 On Thursday, January 29, 2015 6:04 PM, Oz Linden (Scott Lawrence) 
 wrote:
   
 

  On 2015-01-28 19:23 , Callum Prentice (Callum) wrote:
  
  I can try it on an XP system tomorrow when I'm in the office and have access 
to the QA Lab.  
 
 
 To be clear... XP is not supported and if it does not work, that is not a bug.
 
 If it does happen to work, I don't object, but we won't spend time on it if it 
doesn't.
 
 We announced that we'd dropped XP support several months ago.  
 
 -- 
  Oz Linden (Scott Lawrence) | Engineering Director, Second Life
 Email or Hangouts o...@lindenlab.com | Second Life Oz 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

 


 
   ___
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] Viewer Tools Upgrades - with a call for help

2015-01-29 Thread Nicky Perian

It does not run on XP.  The error is that it is nor a valid windows 32 bit 
application.
That brings up another question. Will it run on 32 bit variants of vista and 
win7? 

 On Thursday, January 29, 2015 6:04 PM, Oz Linden (Scott Lawrence) 
 wrote:
   
 

  On 2015-01-28 19:23 , Callum Prentice (Callum) wrote:
  
  I can try it on an XP system tomorrow when I'm in the office and have access 
to the QA Lab.  
 
 
 To be clear... XP is not supported and if it does not work, that is not a bug.
 
 If it does happen to work, I don't object, but we won't spend time on it if it 
doesn't.
 
 We announced that we'd dropped XP support several months ago.  
 
 -- 
  Oz Linden (Scott Lawrence) | Engineering Director, Second Life
 Email or Hangouts o...@lindenlab.com | Second Life Oz 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

 
   ___
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] Viewer Tools Upgrades - with a call for help

2015-01-29 Thread Oz Linden (Scott Lawrence)


On 2015-01-28 19:23 , Callum Prentice (Callum) wrote:
I can try it on an XP system tomorrow when I'm in the office and have 
access to the QA Lab.




To be clear... XP is not supported and if it does not work, that is not 
a bug.


If it does happen to work, I don't object, but we won't spend time on it 
if it doesn't.


We announced that we'd dropped XP support several months ago.

--
*Oz Linden (Scott Lawrence)* | /Engineering Director, Second Life/
Email or Hangouts o...@lindenlab.com  | Second 
Life Oz 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] Viewer Tools Upgrades - with a call for help

2015-01-29 Thread Callum Prentice (Callum)

Yep - we need to add the right set of parameters to 'autobuild' to set up
FMod, Havok QuickTime etc.

Can anyone tell me what they are or point me at the right doc before I
start searching.

On Thu, Jan 29, 2015 at 12:44 PM, Henri Beauchamp  wrote:

> On Thu, 29 Jan 2015 11:45:46 +0100, Henri Beauchamp wrote:
>
> > On Wed, 28 Jan 2015 10:53:11 -0500, Oz Linden (Scott Lawrence) wrote:
> >
> > > We've also put up a new page of instructions on how to set up a Windows
> > > development environment
> > > .
> > > Suggestions for improvement are most welcome here and on the Talk
> > > page... we're trying to keep it as simple as possible while being
> > > sufficient to build a clean checkout of the viewer.
> >
> > Missing bits:
> >
> > - When using Windows 7, you must also update from IE8 to a newer version
> > since else, you can't log in to register for a free license from within
> > Visual Studio 2013 Community (the IE8 Javascript engine fails on two of
> > the scripts used by VS2013).
> >
> > - To compile a viewer, you'll also need FMOD Ex installed.
> >
> > Henri.
>
> I also forgot: there's the Quicktime issue: TPVs need the QuickTime SDK
> (v7.3) installed, since the pre-built library in autobuild.xml is on
> a private (Linden-only) server...
>
> Henri.
> ___
> 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*
*Cell* 650 888 1697 | *Skype* CallumPrentice | *Second Life *Callum 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] Viewer Tools Upgrades - with a call for help

2015-01-29 Thread Henri Beauchamp

On Thu, 29 Jan 2015 11:45:46 +0100, Henri Beauchamp wrote:

> On Wed, 28 Jan 2015 10:53:11 -0500, Oz Linden (Scott Lawrence) wrote:
> 
> > We've also put up a new page of instructions on how to set up a Windows 
> > development environment 
> > .  
> > Suggestions for improvement are most welcome here and on the Talk 
> > page... we're trying to keep it as simple as possible while being 
> > sufficient to build a clean checkout of the viewer.
> 
> Missing bits:
> 
> - When using Windows 7, you must also update from IE8 to a newer version
> since else, you can't log in to register for a free license from within
> Visual Studio 2013 Community (the IE8 Javascript engine fails on two of
> the scripts used by VS2013).
> 
> - To compile a viewer, you'll also need FMOD Ex installed.
> 
> Henri.

I also forgot: there's the Quicktime issue: TPVs need the QuickTime SDK
(v7.3) installed, since the pre-built library in autobuild.xml is on
a private (Linden-only) server...

Henri.
___
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] Viewer Tools Upgrades - with a call for help

2015-01-29 Thread Jonathan Welch

When you have finished installing the compiler there is a button to launch it.

More documentation needed for:
1) You are then asked to sign in or skip that step.
2) You then see a setup page with a dropdown, I changed from General
to C++ hoping that was the right thing to do.

On Thu, Jan 29, 2015 at 5:45 AM, Henri Beauchamp  wrote:
> On Wed, 28 Jan 2015 10:53:11 -0500, Oz Linden (Scott Lawrence) wrote:
>
>> We've also put up a new page of instructions on how to set up a Windows
>> development environment
>> .
>> Suggestions for improvement are most welcome here and on the Talk
>> page... we're trying to keep it as simple as possible while being
>> sufficient to build a clean checkout of the viewer.
>
> Missing bits:
>
> - When using Windows 7, you must also update from IE8 to a newer version
> since else, you can't log in to register for a free license from within
> Visual Studio 2013 Community (the IE8 Javascript engine fails on two of
> the scripts used by VS2013).
>
> - To compile a viewer, you'll also need FMOD Ex installed.
>
> Henri.
> ___
> 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] Viewer Tools Upgrades - with a call for help

2015-01-29 Thread Henri Beauchamp

On Wed, 28 Jan 2015 10:53:11 -0500, Oz Linden (Scott Lawrence) wrote:

> We've also put up a new page of instructions on how to set up a Windows 
> development environment 
> .  
> Suggestions for improvement are most welcome here and on the Talk 
> page... we're trying to keep it as simple as possible while being 
> sufficient to build a clean checkout of the viewer.

Missing bits:

- When using Windows 7, you must also update from IE8 to a newer version
since else, you can't log in to register for a free license from within
Visual Studio 2013 Community (the IE8 Javascript engine fails on two of
the scripts used by VS2013).

- To compile a viewer, you'll also need FMOD Ex installed.

Henri.
___
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] Viewer Tools Upgrades - with a call for help

2015-01-29 Thread Nicky Perian

bill@billAW ~Is going to be necessary to use autobuild.cmd from cygwin?$ 
autobuild --versionC:\Python27\python.exe: can't open file 
'/cygdrive/c/Users/bill/autobuild-metadata/bin/autobuild': [Errno 2] No such 
file or directory
bill@billAW ~$ autobuild.cmd --versionautobuild 1.0

bill@billAW ~$ which 
autobuild/cygdrive/c/Users/bill/autobuild-metadata/bin/autobuild
bill@billAW ~$ cd autobuild-metadata
bill@billAW ~/autobuild-metadata$ hg tipchangeset:   715:9332634373d2tag:       
  tipuser:        Nat Goodspeed date:        Wed Jan 07 
16:05:14 2015 -0500summary:     Remove cygdrive/cygpath kludges from a couple 
places in autobuild.

bill@billAW ~/autobuild-metadata$

 On Thursday, January 29, 2015 1:18 AM, Lance Corrimal 
 wrote:

 Am Mittwoch 28 Januar 2015, 18:11:48 schrieb Jonathan Welch:
> From something Tank said at a meeting: will the resulting executable
> run on an XP system?  If not a note should be put in somewhere about
> this restriction.

...ahem

Windows XP is End Of Life, has been for quite some time, security holes are 
NOT fixed anymore, and anyone who still uses XP on a computer that is in any 
form shape or size connected to the internet should be drowned in his own 
drool.

just my two cents.
___
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] Viewer Tools Upgrades - with a call for help

2015-01-28 Thread Lance Corrimal

Am Mittwoch 28 Januar 2015, 18:11:48 schrieb Jonathan Welch:
> From something Tank said at a meeting: will the resulting executable
> run on an XP system?  If not a note should be put in somewhere about
> this restriction.

...ahem

Windows XP is End Of Life, has been for quite some time, security holes are 
NOT fixed anymore, and anyone who still uses XP on a computer that is in any 
form shape or size connected to the internet should be drowned in his own 
drool.


just my two cents.
___
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] Viewer Tools Upgrades - with a call for help

I got through the list on the wiki with some slight modifications. Here are my 
changes: 
 At first I got 4 errors, which all got resolved when I installed the 32bit 
cigwin with the same additional packages mentioned for the 64bit.  

For Direct X I didn't install the SDK mentioned in the wiki, and instead used 
the windows 8.1 SDK, but I had to modify DirectX.cmake to find the files I the 
new folder (something I had done a while ago in FS, so I just copied that file 
from FS on over to the new LL repo).   It still spits out a bunch of warnings, 
but it does 
work.http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/file/11f977e832dd/indra/cmake/DirectX.cmake
I also used Tortus HG 3.2.4 and cmake 3.1.1 (both the latest stable)
~TM   ___
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] Viewer Tools Upgrades - with a call for help

2015-01-28 Thread Melissa Browne

Thanks Jonathan you were right, opening a new command widow allowed the process 
to find autobuild. Unfortunately, now when I try to build, the window gets 
flooded with the following CMake error :
CMake Error at cmake/00-Common.cmake:47 (string):
  string sub-command REPLACE requires at least four arguments.
Call Stack (most recent call first):
  newview/CMakeLists.txt:5 (include)
Any ideas on this?
MB___
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] Viewer Tools Upgrades - with a call for help

they are just warning,  you can ignore them.~TM

From: moonbots...@centurylink.net
To: opensource-dev@lists.secondlife.com
Date: Wed, 28 Jan 2015 21:13:45 -0600
Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help

Thanks 
Jonathan you were right, opening a new command widow allowed the process to 
find 
autobuild. Unfortunately, now when I try to build, the window gets flooded with 
the following CMake error :
CMake Error at cmake/00-Common.cmake:47 (string):
  string sub-command REPLACE requires at least four arguments.
Call Stack (most recent call first):
  newview/CMakeLists.txt:5 (include)
Any ideas on this?
MB

___
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] Viewer Tools Upgrades - with a call for help

I can try it on an XP system tomorrow when I'm in the office and have
access to the QA Lab.

On Wed, Jan 28, 2015 at 3:11 PM, Jonathan Welch  wrote:

> From something Tank said at a meeting: will the resulting executable
> run on an XP system?  If not a note should be put in somewhere about
> this restriction.
>
> On 1/28/15, Callum Prentice (Callum)  wrote:
> > Thanks for the clarification Darien - my working assumption TankMaster is
> > that those libs/headers are pulled in via some CMake magic - I'll go
> check
> > to see if that's the case.
> >
> > On Wed, Jan 28, 2015 at 1:25 PM, Tank Master 
> > wrote:
> >
> >> As far as I know, it is only used to detect the GPU name in windows.
> >> Also, if the compile IS using the DX 2010 SDK, there is no documentation
> >> on
> >> modifying VS2013 to point to it, which make me wonder if the build
> >> environment is even using the files, let alone seeing them.
> >> ~TM
> >> --
> >> Date: Wed, 28 Jan 2015 13:22:33 -0800
> >> From: darien.caldw...@gmail.com
> >> To: opensource-dev@lists.secondlife.com
> >> Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for
> >> help
> >>
> >> Oh and DXERR is removed as well.
> >>
> >> On Wed, Jan 28, 2015 at 1:21 PM, Darien Caldwell <
> >> darien.caldw...@gmail.com> wrote:
> >>
> >> The windows 8.1 version of the DirectX SDK removes the D3DX* library and
> >> changes XNAMath to DirectXMath, so if you use either from those
> >> namespaces,
> >> it's not going to work.  I don't know exactly what the viewer is using
> >> DirectX for, but as long as it's not using anything from the
> >> removed/renamed libraries, it should be fine to change over.
> >>
> >>
> >>
> >> ___ 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
> >>
> >
> >
> >
> > --
> > *Callum Prentice *| *Software Engineer*
> > *Cell* 650 888 1697 | *Skype* CallumPrentice | *Second Life *Callum
> Linden
> >
> > Linden Lab <http://www.lindenlab.com/> | Makers of Shared Creative
> Spaces
> >
> > Check out what we're working on! <http://lindenlab.com/products>
> >
>



-- 
*Callum Prentice *| *Software Engineer*
*Cell* 650 888 1697 | *Skype* CallumPrentice | *Second Life *Callum Linden

Linden Lab <http://www.lindenlab.com/> | Makers of Shared Creative Spaces

Check out what we're working on! <http://lindenlab.com/products>
___
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] Viewer Tools Upgrades - with a call for help

looks like on windows 10, a full reboot is needed to puck up changes to the 
path... annoying to say the least.  simply restarting the command prompt wasn't 
enough for me.
~TM
From: moonbots...@centurylink.net
To: opensource-dev@lists.secondlife.com
Date: Wed, 28 Jan 2015 14:19:11 -0600
Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help

Has anyone that has tried to build the viewer per the how 
to set up a Windows development environment instructions ran into autobuild 
not being recognized? Following the instructions line by line, everything 
before 
the Autobuild Configure section checks out as set and installed correctly 
including setting the path in the environment settings. Is there something 
possibly missing in the instructions for us noobs?

MB

___
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] Viewer Tools Upgrades - with a call for help

2015-01-28 Thread Jonathan Welch

>From something Tank said at a meeting: will the resulting executable
run on an XP system?  If not a note should be put in somewhere about
this restriction.

On 1/28/15, Callum Prentice (Callum)  wrote:
> Thanks for the clarification Darien - my working assumption TankMaster is
> that those libs/headers are pulled in via some CMake magic - I'll go check
> to see if that's the case.
>
> On Wed, Jan 28, 2015 at 1:25 PM, Tank Master 
> wrote:
>
>> As far as I know, it is only used to detect the GPU name in windows.
>> Also, if the compile IS using the DX 2010 SDK, there is no documentation
>> on
>> modifying VS2013 to point to it, which make me wonder if the build
>> environment is even using the files, let alone seeing them.
>> ~TM
>> --
>> Date: Wed, 28 Jan 2015 13:22:33 -0800
>> From: darien.caldw...@gmail.com
>> To: opensource-dev@lists.secondlife.com
>> Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for
>> help
>>
>> Oh and DXERR is removed as well.
>>
>> On Wed, Jan 28, 2015 at 1:21 PM, Darien Caldwell <
>> darien.caldw...@gmail.com> wrote:
>>
>> The windows 8.1 version of the DirectX SDK removes the D3DX* library and
>> changes XNAMath to DirectXMath, so if you use either from those
>> namespaces,
>> it's not going to work.  I don't know exactly what the viewer is using
>> DirectX for, but as long as it's not using anything from the
>> removed/renamed libraries, it should be fine to change over.
>>
>>
>>
>> ___ 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
>>
>
>
>
> --
> *Callum Prentice *| *Software Engineer*
> *Cell* 650 888 1697 | *Skype* CallumPrentice | *Second Life *Callum Linden
>
> Linden Lab <http://www.lindenlab.com/> | Makers of Shared Creative Spaces
>
> Check out what we're working on! <http://lindenlab.com/products>
>
___
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] Viewer Tools Upgrades - with a call for help

Thanks for the clarification Darien - my working assumption TankMaster is
that those libs/headers are pulled in via some CMake magic - I'll go check
to see if that's the case.

On Wed, Jan 28, 2015 at 1:25 PM, Tank Master  wrote:

> As far as I know, it is only used to detect the GPU name in windows.
> Also, if the compile IS using the DX 2010 SDK, there is no documentation on
> modifying VS2013 to point to it, which make me wonder if the build
> environment is even using the files, let alone seeing them.
> ~TM
> --
> Date: Wed, 28 Jan 2015 13:22:33 -0800
> From: darien.caldw...@gmail.com
> To: opensource-dev@lists.secondlife.com
> Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help
>
> Oh and DXERR is removed as well.
>
> On Wed, Jan 28, 2015 at 1:21 PM, Darien Caldwell <
> darien.caldw...@gmail.com> wrote:
>
> The windows 8.1 version of the DirectX SDK removes the D3DX* library and
> changes XNAMath to DirectXMath, so if you use either from those namespaces,
> it's not going to work.  I don't know exactly what the viewer is using
> DirectX for, but as long as it's not using anything from the
> removed/renamed libraries, it should be fine to change over.
>
>
>
> ___ 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
>



-- 
*Callum Prentice *| *Software Engineer*
*Cell* 650 888 1697 | *Skype* CallumPrentice | *Second Life *Callum Linden

Linden Lab <http://www.lindenlab.com/> | Makers of Shared Creative Spaces

Check out what we're working on! <http://lindenlab.com/products>
___
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] Viewer Tools Upgrades - with a call for help

As far as I know, it is only used to detect the GPU name in windows.  Also, if 
the compile IS using the DX 2010 SDK, there is no documentation on modifying 
VS2013 to point to it, which make me wonder if the build environment is even 
using the files, let alone seeing them.
~TM
Date: Wed, 28 Jan 2015 13:22:33 -0800
From: darien.caldw...@gmail.com
To: opensource-dev@lists.secondlife.com
Subject: Re: [opensource-dev] Viewer Tools Upgrades - with a call for help

Oh and DXERR is removed as well.
On Wed, Jan 28, 2015 at 1:21 PM, Darien Caldwell  
wrote:
The windows 8.1 version of the DirectX SDK removes the D3DX* library and 
changes XNAMath to DirectXMath, so if you use either from those namespaces, 
it's not going to work.  I don't know exactly what the viewer is using DirectX 
for, but as long as it's not using anything from the removed/renamed libraries, 
it should be fine to change over.

___
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] Viewer Tools Upgrades - with a call for help

2015-01-28 Thread Darien Caldwell

Oh and DXERR is removed as well.

On Wed, Jan 28, 2015 at 1:21 PM, Darien Caldwell 
wrote:

> The windows 8.1 version of the DirectX SDK removes the D3DX* library and
> changes XNAMath to DirectXMath, so if you use either from those namespaces,
> it's not going to work.  I don't know exactly what the viewer is using
> DirectX for, but as long as it's not using anything from the
> removed/renamed libraries, it should be fine to change over.
>
___
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] Viewer Tools Upgrades - with a call for help

2015-01-28 Thread Darien Caldwell

The windows 8.1 version of the DirectX SDK removes the D3DX* library and
changes XNAMath to DirectXMath, so if you use either from those namespaces,
it's not going to work.  I don't know exactly what the viewer is using
DirectX for, but as long as it's not using anything from the
removed/renamed libraries, it should be fine to change over.
___
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] Viewer Tools Upgrades - with a call for help

Thank you Jonathan - you're right - there should be more notes on how to
download and configure the Community version. For the Pro version we use
here,  I note in the doc that "Uncheck all the "Optional features to
install:" - they are not required" - the same sort of thing along with
notes on the local/downloader version would help - can you put something
together?

Perhaps you can clarify what needs to be improved in the Autobuild and
Python sections? Reads okay to me but it's sometimes hard to see what's
wrong when you're close to it.

Looks like the Todo note about  autobuild configure options for packages
like FMod and Havok was removed when the doc was moved from our internal
wiki - can you outline what you'd like to see there and I'll add it.

On Wed, Jan 28, 2015 at 12:25 PM, Jonathan Welch  wrote:

> I've read over the instructions and have started the install process
> on a fresh VM.  Some notes:
>
> These instructions should be written assuming the person reading them
> is not a developer...yet, but does know their way around when
> installing software.
>
> The yellow info window talks about requirements for installing
> windows.  Let's drop that part and just list what windows version(s)
> these instructions work on.
>
> The term Cygwin shell is not defined, nor how to access it.
>
> Let's only have one set of installation instructions, and that for a
> package everyone can access: the Community version of the compiler.
> If you own a better version of this compiler then you are probably
> smart enough to figure out what different/additional steps to perform.
>
> No mention is made about the online vs offline versions of the
> Community file you can download.  I picked up the offline version,
> which took over two hours to download.  If I ever needed to reinstall
> this software or if there was some hiccup in the installation process
> I would not want to repeat that long download again using the online
> method.
>
> Very important -- when installing the compiler do I need to also
> install all those additional optional features that are automatically
> checked and which take up precious space on my drive?
>
> As an addendum to pulling in the offline version, mention should be
> made on where to pick up a free package that lets you mount this .ISO
> file without first having to burn a disc.
>
> The instructions for setting up Autobuild and Python need some editing
> for grammar, clarity, and consistency.
>
> NSIS should be under an Optional heading.
>
> No mention is made about FmodEX -- have these instructions been tested
> outside of the lindenlab.com domain?  I suspect an additional section
> will be necessary for this package.
>
> Okay, more later, once I have made some additional progress.
>
> -jonathan
> ___
> 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*
*Cell* 650 888 1697 | *Skype* CallumPrentice | *Second Life *Callum 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] Viewer Tools Upgrades - with a call for help

Did you add the C:\Python27\Scripts folder (or wherever you installed
Python) to your path after you 'pip installed' autobuild?  Sounds like you
did but that's the only thing I can think of.

On Wed, Jan 28, 2015 at 12:19 PM, Melissa Browne <
moonbots...@centurylink.net> wrote:

>   Has anyone that has tried to build the viewer per the how to set up a
> Windows development environment instructions ran into autobuild not being
> recognized? Following the instructions line by line, everything before the
> Autobuild Configure section checks out as set and installed correctly
> including setting the path in the environment settings. Is there something
> possibly missing in the instructions for us noobs?
>
> MB
>
> ___
> 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*
*Cell* 650 888 1697 | *Skype* CallumPrentice | *Second Life *Callum 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] Viewer Tools Upgrades - with a call for help

>
> None of the "right click and run as administrator" is needed; when the
> installer needs admin rights to install, it will prompt to do so.
>

In the past, I've noticed subtle differences in the behavior of packages
when you don't explicitly run the installer as an administrator and when
you do.  Unless you have a strong objection, I'd like to leave those lines
in there until we're sure.

DX SDK 2010 is not used if you are using the windows 8 SDK or higher (DX
> SDK is integrated into windows SDK 8.0 and higher); both VS community and
> VS 2013 ultimate install Windows SDK 8.1 and therefore will use the DX there
>

Interesting - I do see DX headers and libs in the "C:\Program Files
(x86)\Windows Kits\8.1" folders. Do you know for sure that builds complete
without the separate SDK? If so, we should remove the reference to it -
it's huge.



> The linked update for Visual studio 2013 points to update 5 CTP; this is a
> preview and should not be used for production environment.  It should point
> to:
> http://www.visualstudio.com/en-us/downloads/download-visual-studio-vs#DownloadFamilies_5
> which will list the latest stable update.
>

Good point - noted. and I will change the wiki.

A note to run Microsoft Update with the option of installing updates for
> other Microsoft products should be included in the last step of installing
> VS 2013.  This will update all the installed applications from VS 2013 like
> SQL server and VS itself.
>

Good idea. I'd like to document how to enable that - all I see in Windows
Update -> Settings are options to change how and when they're updated. Do
you know how to change what gets checked?


> I will probably have other recommendations after trying the wiki out on a
> fresh system that hasn't been tainted with the 2010 build process.
>

Great stuff. Thanks TankMaster.


-- 
*Callum Prentice *| *Software Engineer*
*Cell* 650 888 1697 | *Skype* CallumPrentice | *Second Life *Callum 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] Viewer Tools Upgrades - with a call for help

2015-01-28 Thread Jonathan Welch

If you change your path the instructions fail to mention that you have
to open a new command window to pick up those changes -- could that be
your problem?

On 1/28/15, Melissa Browne  wrote:
> Has anyone that has tried to build the viewer per the how to set up a
> Windows development environment instructions ran into autobuild not being
> recognized? Following the instructions line by line, everything before the
> Autobuild Configure section checks out as set and installed correctly
> including setting the path in the environment settings. Is there something
> possibly missing in the instructions for us noobs?
>
> MB
___
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] Viewer Tools Upgrades - with a call for help

2015-01-28 Thread Jonathan Welch

I've read over the instructions and have started the install process
on a fresh VM.  Some notes:

These instructions should be written assuming the person reading them
is not a developer...yet, but does know their way around when
installing software.

The yellow info window talks about requirements for installing
windows.  Let's drop that part and just list what windows version(s)
these instructions work on.

The term Cygwin shell is not defined, nor how to access it.

Let's only have one set of installation instructions, and that for a
package everyone can access: the Community version of the compiler.
If you own a better version of this compiler then you are probably
smart enough to figure out what different/additional steps to perform.

No mention is made about the online vs offline versions of the
Community file you can download.  I picked up the offline version,
which took over two hours to download.  If I ever needed to reinstall
this software or if there was some hiccup in the installation process
I would not want to repeat that long download again using the online
method.

Very important -- when installing the compiler do I need to also
install all those additional optional features that are automatically
checked and which take up precious space on my drive?

As an addendum to pulling in the offline version, mention should be
made on where to pick up a free package that lets you mount this .ISO
file without first having to burn a disc.

The instructions for setting up Autobuild and Python need some editing
for grammar, clarity, and consistency.

NSIS should be under an Optional heading.

No mention is made about FmodEX -- have these instructions been tested
outside of the lindenlab.com domain?  I suspect an additional section
will be necessary for this package.

Okay, more later, once I have made some additional progress.

-jonathan
___
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] Viewer Tools Upgrades - with a call for help

2015-01-28 Thread Melissa Browne

Has anyone that has tried to build the viewer per the how to set up a Windows 
development environment instructions ran into autobuild not being recognized? 
Following the instructions line by line, everything before the Autobuild 
Configure section checks out as set and installed correctly including setting 
the path in the environment settings. Is there something possibly missing in 
the instructions for us noobs?

MB___
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] Viewer Tools Upgrades - with a call for help