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
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
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
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 wi
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
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: R
>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/he
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 window
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 2
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
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
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
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
>
> 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
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
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
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
A few things I noticed right off:
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.
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);
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
19 matches
Mail list logo
