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

On 2015-02-27 20:24 , Nicky Perian wrote: Will we have to keep the old tools active to rebuild the plugin binaries and then piece together archives to use in the new tools? If so, that is unsatisfactory. 3p-update-slplugins needs to standalone and be able to produce an archive without having to r

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

> On 2015-02-24 17:10 , Henri Beauchamp wrote: > > On Tue, 24 Feb 2015 15:37:21 -0600, Nicky Perian wrote: > > > >> Plugins are no longer built in the viewer but, are delivered > >> as content in an archive. > > Which means TPV developers will not be able any more to fix bugs in the > > plugins and

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

On Fri, 27 Feb 2015 09:23:19 -0500, Oz Linden (Scott Lawrence) wrote: > On 2015-02-24 17:10 , Henri Beauchamp wrote: > > On Tue, 24 Feb 2015 15:37:21 -0600, Nicky Perian wrote: > > > >> Plugins are no longer built in the viewer but, are delivered > >> as content in an archive. > > Which means TPV

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

On 2015-02-24 17:10 , Henri Beauchamp wrote: On Tue, 24 Feb 2015 15:37:21 -0600, Nicky Perian wrote: Plugins are no longer built in the viewer but, are delivered as content in an archive. Which means TPV developers will not be able any more to fix bugs in the plugins and will have to endure th

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

Yeah but don't really have to use codecs. HTML5 Elements for audio do not use codecs, not in most of the larger browsers anyway (Chrome, IE). The mp3 stream is played natively by the browser. ( it's true Firefox does not include native MP3 support) It would require for LL to finish their project

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

On February 25, 2015 at 6:49:56 AM, Henri Beauchamp (sl...@free.fr) wrote: On Tue, 24 Feb 2015 19:03:29 -0800, Darien Caldwell wrote:  > I'm pretty sure the reasoning behind LL moving all the multimedia to a  > plugin system was so that 3rd parties could write their own plugins.  I doubt it...  Y

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

On Tue, 24 Feb 2015 19:03:29 -0800, Darien Caldwell wrote: > I'm pretty sure the reasoning behind LL moving all the multimedia to a > plugin system was so that 3rd parties could write their own plugins. I doubt it... > There's nothing stopping anyone from writing a plugin to take over all > the

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

I'm pretty sure the reasoning behind LL moving all the multimedia to a plugin system was so that 3rd parties could write their own plugins. There's nothing stopping anyone from writing a plugin to take over all the functions the old Quicktime plugin does. It's just that nobody has bothered to do it

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

The problem is the SDK is so old, it is not compatible with VS2013 do to the updated VC11 code support. That why it is erroring now.~TM > Date: Tue, 24 Feb 2015 23:10:20 +0100 > From: sl...@free.fr > To: opensource-dev@lists.secondlife.com > Subject: Re: [opensource-dev] Viewer To

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

On Tue, 24 Feb 2015 15:37:21 -0600, Nicky Perian wrote: > Plugins are no longer built in the viewer but, are delivered > as content in an archive. Which means TPV developers will not be able any more to fix bugs in the plugins and will have to endure the very same bugs as the ones plagging LL's v

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

Plugins are no longer built in the viewer but, are delivered as content in an archive. For quicktime this is more licence friendly by delivering the dll instead on the components needed to build the dll in the viewer. That is likely not the complete reason for packaging but, it is cleaner. Once LL

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

Recently I started working on getting set up with VS2013 build system and I have it running fairly smoothly. I have with the help of another member on this list gotten it so that I can build the plug-ins including QuickTime(prop 3-p lib) which you have to have the sdk installed on your system. Now

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

While the signup does require a birth date (any birth date, hint-hint), the phone Number is optional. On Sun, Feb 22, 2015 at 2:58 AM, Jonathan Welch wrote: > Yes, the warning window says what to do, but it was only by chance > that I saw that message, so better to have mention of this necessa

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

Yes, the warning window says what to do, but it was only by chance that I saw that message, so better to have mention of this necessary step in the instructions than to have your compiler fail to run. Also, some people may not want to supply a birthdate and phone number, so before they begin this

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

On February 21, 2015 at 5:50:42 PM, Jonathan Welch (jhwe...@gmail.com) wrote: I just started up VS2013 and was exploring some of the windows and  menus and discovered that my trial license is only good for 30 days.  The instructions should cover what to do to obtain a long-term  license.  Warning

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

I just started up VS2013 and was exploring some of the windows and menus and discovered that my trial license is only good for 30 days. The instructions should cover what to do to obtain a long-term license. Warning window: http://i.imgur.com/RwTzJxH.png ___

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

In case this bug was missed and/or not fixed the first time I reported it here it is again. The first time building does not succeed: -- Build started: Project: copy_w_viewer_manifest, Configuration: Release Win32 -- Building Custom Rule E:/ss/STORM-0/indra/newview/CMakeLists.txt CMak

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

Just a fyi, until the error in the file copy section is fixed (reported earlier in this thread) the first build fails with one error. The second time you build, the files are copied and you are then good to go. ___ Policies and (un)subscribe information

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

On 2015-02-07 21:08 , Jonathan Welch wrote: Also, I am curious: is all this pip and easy install business doing more than just fetching autobuild.exe? It depends on whether or not your system already has all the prerequisites that autobuild needs (which have changed). The point of using pip

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

On Mon, Feb 9, 2015 at 3:59 AM, Nicky D. wrote: > >> Autobuild is installed into Python27/scripts -- can this be moved out >> of that package's tree? >> >> > You can try to install it into its own virtual-env. > Mmhmm. I wanted more communication about conversion of C++, python, and other scrip

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

> > > Autobuild is installed into Python27/scripts -- can this be moved out > of that package's tree? > > You can try to install it into its own virtual-env. I do that with llbase. autobuild itself I run just from a bitbucket clone. So I did not try to put it into a virtual-env, but that should too

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

> Autobuild is installed into Python27/scripts -- can this be moved out > of that package's tree? > > No, that's where Python wants it. > Just for fun I moved the Scripts directory out from under where python is installed, adjusted my path accordingly, and was able to configure and compile just fi

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

Ok, well, I'll be sad to see lscript go, I had some good times there, but it makes sense. ___ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated

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

On 2/7/2015 8:09 PM, Argent Stonecutter wrote: > Doesn't the script editor use it for syntax coloring? Or has it > dropped back to using a more simplistic algorithm? The highlight info is now supplied by app_settings/keywords_lsl_default.xml, with updates downloaded from the server as needed. So

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

On February 7, 2015 at 6:09:54 PM, Argent Stonecutter (secret.arg...@gmail.com) wrote: On 2015-02-07, at 16:24, Cinder Roxley wrote:  > 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

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

On 2015-02-07, at 16:24, Cinder Roxley wrote: > 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 depe

Re: [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

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 t

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

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

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 t

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 personall

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

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 li

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

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

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

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.

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

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

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

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

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

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

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/d

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

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 D

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

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 tim

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

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 thr

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 presen

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

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

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 wi

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

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

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

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

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 Expr

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

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 wi

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

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

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

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

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

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 in

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

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 w

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

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 t

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

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, Jona

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

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

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

ION}"}' > ${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] View

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

*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!

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

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

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

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

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

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 20

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 -

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

oolset=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 Upgrad

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

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 h

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

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 s

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

STS: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 “ERRO

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/

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

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 autobu

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

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 au

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

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

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

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 Prenti

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 tim

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 Beauc

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

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

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

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

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

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 a

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

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 ~$ w

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

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, secur

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, an

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

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

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

odifying 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

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

bject: 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

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

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 Caldwel

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

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

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

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

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 t

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

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 li

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

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

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 d

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

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 i

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

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

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 includi

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

opensource-dev@lists.secondlife.com 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 las

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 OS

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

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 * Al