On Fri, Jan 21, 2011 at 6:40 PM, Nicky Perian <nickyper...@yahoo.com> wrote:
> I am trying to prove a no harm done 2005 build first. Then on to 2010. > the build-cmd.sh script references "build_sln" for several entries. > Example: build_sln src/client/windows/breakpad_client.sln "release|win32" > exception_handler > > These all fail when I try them. Is build_sln common to the LL build system > and not included in 3p-google-breakpad source? > > The sln files build with cd src/client/windows > ../../tools/gyp/gyp -G msvs_version=2005 > > Is this just and automation thingy? > Can I just build with debug and release or do I need build_sln's magic? > Nicky > > Yes, it's for automation. The shell function build_sln is part of our new third party lib build system which we're starting to document here: http://wiki.secondlife.com/wiki/Autobuild and here: http://wiki.secondlife.com/wiki/Autobuild_How_To You're a bit ahead of the curve, and we haven't quite kicked all of this off with great fanfare just yet. But thanks for diving in fearlessly :) If you want to run the build, in theory you should just need to check out our autobuild repository <http://bitbucket.org/lindenlab/autobuild>, put its bin directory in your PATH, and run 'autobuild install && autobuild build && autobuild package' Anyways, in addition to that, a simple substitute definition for the function is as follows: build_sln() { local solution=$1 local config=$2 local proj=$3 if [ -z "$proj" ] ; then devenv.com "$(cygpath -m "$solution")" /build "$config" else devenv.com "$(cygpath -m "$solution")" /build "$config" /project "$proj" fi } -Brad
_______________________________________________ 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
