No subject


Wed Apr 28 21:25:55 PDT 2010


avalible only if you can connect to LL's internal VPN.
As for the name of the exe, express does not have "devenv.exe" and i
dont think the "VCExpress.exe" exe will work.

On Thu, Jan 27, 2011 at 5:25 PM, WolfPup Lowenhar
<wolfpup67 at earthlink.net> wrote:
> Meant to sent this to the list and not just Oz.
>
>
>
> From: WolfPup Lowenhar [mailto:wolfpup67 at earthlink.net]
> Sent: Thursday, January 27, 2011 7:46 PM
> To: 'Oz Linden (Scott Lawrence)'
> Subject: RE: [opensource-dev] Using 'autobuild' to build the viewer
>
>
>
> C:\Program Files\Microsoft Visual Studio 8\Common7\Tools>vsvars32.bat
>
> Setting environment for using Microsoft Visual Studio 2005 x86 tools.
>
>
>
> C:\Program Files\Microsoft Visual Studio 8\Common7\Tools>path
>
> PATH=3DC:\Program Files\Microsoft Visual Studio 8\Common7\IDE;
>
> C:\Program Files\Microsoft Visual Studio 8\VC\BIN;
>
> C:\Program Files\Microsoft Visual Studio 8\Common7\Tools;
>
> C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\bin;
>
> C:\Program Files\Microsoft Visual Studio 8\VC\PlatformSDK\bin;
>
> C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin;
>
> C:\Windows\Microsoft.NET\Framework\v2.0.50727;
>
> C:\Program Files\Microsoft Visual Studio 8\VC\VCPackages;
>
> C:\Program Files\Common Files\Microsoft Shared\Windows Live;
>
> C:\Perl\site\bin;C:\Perl\bin;C:\Python26\Scripts;C:\Python26\;C:\Windows\=
system32;
>
> C:\Windows;C:\Windows\System32\Wbem;
>
> C:\Windows\System32\WindowsPowerShell\v1.0\;
>
> C:\Program Files\Intel\DMIX;
>
> c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;
>
> c:\Program Files\Microsoft SQL Server\100\DTS\Binn\;
>
> C:\Program Files\CMake 2.8\bin;
>
> C:\Program Files\TortoiseSVN\bin;
>
> C:\Program Files\GtkSharp\2.12\bin;
>
> C:\Program Files\QuickTime\QTSystem\;
>
> C:\Program Files\Windows Live\Shared;
>
> C:\Program Files\TortoiseHg\;
>
> C:\Users\Brendan\AppData\Roaming\Python\Scripts
>
>
>
> C:\Program Files\Microsoft Visual Studio 8\Common7\Tools>cd
> D:\HG\viewer-autobuild
>
>
>
> C:\Program Files\Microsoft Visual Studio 8\Common7\Tools>d:
>
>
>
> D:\HG\viewer-autobuild>autobuild configure -c OpenSourceRelWithDebInfo
>
> Traceback (most recent call last):
>
> =C2=A0 File "C:\Python26\Scripts\autobuild", line 35, in <module>
>
> =C2=A0=C2=A0=C2=A0 from autobuild.autobuild_main import Autobuild
>
> =C2=A0 File "C:\Python26\lib\site-packages\autobuild\autobuild_main.py", =
line 25,
> in <module>
>
> =C2=A0=C2=A0=C2=A0 import common
>
> =C2=A0 File "C:\Python26\lib\site-packages\autobuild\common.py", line 575=
, in
> <module>
>
> =C2=A0=C2=A0=C2=A0 Bootstrap()
>
> =C2=A0 File "C:\Python26\lib\site-packages\autobuild\common.py", line 557=
, in
> __init__
>
> =C2=A0=C2=A0=C2=A0 if download_package(url):
>
> =C2=A0 File "C:\Python26\lib\site-packages\autobuild\common.py", line 237=
, in
> download_package
>
> =C2=A0=C2=A0=C2=A0 scp_or_http =3D __SCPOrHTTPHandler(get_default_scp_com=
mand())
>
> =C2=A0 File "C:\Python26\lib\site-packages\autobuild\common.py", line 106=
, in
> get_default_scp_command
>
>
>
> =C2=A0=C2=A0=C2=A0 raise AutobuildError("cannot find an appropriate scp o=
r pscp command")
>
> autobuild.common.AutobuildError: cannot find an appropriate scp or pscp
> command
>
>
>
> From: opensource-dev-bounces at lists.secondlife.com
> [mailto:opensource-dev-bounces at lists.secondlife.com] On Behalf Of Oz Lind=
en
> (Scott Lawrence)
> Sent: Thursday, January 27, 2011 6:42 PM
> To: opensource-dev
> Subject: [opensource-dev] Using 'autobuild' to build the viewer
>
>
>
> We now have changes ready for building the viewer with the new Linden Lab
> "autobuild" tool (not to be confused with any other similarly named tool
> written by anyone else).=C2=A0 Autobuild is a framework for maintaining a=
nd
> building libraries and other programs. It acts as director providing a
> common interface to build and package libraries and programs, but it is n=
ot
> a build system like make or cmake (it uses them "under the covers").
>
> The autobuild framework has now been applied to the viewer build as a who=
le,
> so that we'll soon have a common command-line method to build on all
> platforms.
>
> Once these changes are merged, you'll be able to build with just two
> commands starting from a clean checkout: one to configure (which only nee=
d
> be done once in each working copy), and one to actually do the build.
>
> To configure your clean working copy:
>
> A default Linden developer build:
>
> autobuild configure -c RelWithDebInfo
>
> A default non-Linden developer build:
>
> autobuild configure -c OpenSourceRelWithDebInfo
>
> A "standalone" non-Linden developer build:
>
> autobuild configure -c OpenSourceStandaloneRelWithDebInfo
>
> Needless to say, there are ways to provide more detailed and fine-grained
> controls, and there are other possible targets for the -c (--configuratio=
n)
> option.
>
> The actual build command is:
>
> autobuild build -c OpenSourceRelWithDebInfo
>
> Most of the components that the viewer depends on have either been conver=
ted
> to building with autobuild, or are in the process of being converted.=C2=
=A0 The
> open source dependencies will eventually all be in bitbucket.org/lindenla=
b
> (aka hg.secondlife.com) repositories; many are already there, and you bui=
ld
> each of them in exactly the same way.
>
> To begin experimenting with this new way of doing things, you'll need to
> check out autobuild itself (it's written in python, and is open source)
> from:
>
> https://bitbucket.org/lindenlab/autobuild
>
> You can either run it directly from the checkout, or install it as a norm=
al
> python package using the command:
>
> setup.py install
>
> There are some pages on the wiki that describe how to use autobuild; like
> all wiki content, improvements are welcome.
>
> The viewer repository modified to use autobuild is at:
>
> https://bitbucket.org/mani_linden/viewer-autobuild
>
> How soon this is merged into viewer-development depends in large part on =
the
> feedback we get from this email, but our hope is that it will be very soo=
n.
> When it is merged, this will be the only "supported" way to build the vie=
wer
> - which is to say that:
>
> Doing it any other idiosyncratic way is up to you and contributions to
> support them are ok as long as they don't break the supported method.
> All contributions must build cleanly using the supported method.
>
> If you are on windows, you must ensure that the Visual Studio executable
> (devenv.com) is in the path that the shell you run autobuild in is using.
> You can set the path using the 'vsvars32.bat' file, found in the director=
y
> referenced by the variable VSxxCOMNTOOLS, where 'xx' depends on the versi=
on
> of VS that you're using (the "supported" value is still '80', but upgradi=
ng
> that is coming real soon now....).
>
> So... download and try these out.=C2=A0 Feedback to the list rather than =
jira
> issues until we merge this into viewer-development, please.
>
> ________________________________
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1204 / Virus Database: 1435/3406 - Release Date: 01/27/11
>
> _______________________________________________
> 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
>


More information about the opensource-dev mailing list