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 <cin...@alchemyviewer.org> 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
