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 present in Express. {code} environment = self.find_visual_studio() if environment == '': environment = self.find_visual_studio_express() if environment == '': environment = self.find_visual_studio_express_single() if environment == '': print >> sys.stderr, "Something went very wrong during build stage, could not find a Visual Studio?" else: build_dirs=self.build_dirs() print >> sys.stderr, "\nSolution generation complete, it can can now be found in:", build_dirs[0] print >> sys.stderr, "\nAs you are using an Express Visual Studio, the build step cannot be automated" print >> sys.stderr, "\nPlease see https://wiki.secondlife.com/wiki/Microsoft_Visual_Studio#Extra_steps_for_Visual_Studio_Express_editions for Visual Studio Express specific information" exit(0)
# devenv.com is CLI friendly, devenv.exe... not so much. return ('"%sdevenv.com" %s.sln /build %s' % (self.find_visual_studio(), self.project_name, self.build_type)) {code} On Wed, Feb 4, 2015 at 1:27 PM, Nicky Perian <nickyper...@gmail.com> wrote: > 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 <cin...@alchemyviewer.org> > 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 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 note on MS's web page for >> Denenv indicate that MSBuild should be used. That note has been present >> since VS2010 release. My thoughts are that the note was there with aim of >> easing the transition for C# and .NET developers that had historically used >> MSBuild into C++. >> >> One additional point. Singularity Viewer project still uses develop.py >> and it internally calls devenv.com with no bad result, as far as I know. >> >> For the list: >> Should autobuild.xml call MSBuild or Devenv? >> >> >> Hi, >> >> You keep asking this question expecting another response, I guess. As >> stated both here and on jira, Microsoft recommends MSBuild going forward. >> All major build server products use MSBuild. Singularity uses MSBuild and >> only falls back to devenv.exe when MSBuild is not available or broken. VS >> Express is a dead product as Microsoft will no longer be making new >> versions of it. >> >> VC projects can be slower on MSBuild because it has to do some backflips >> to build them (they’re not in MSBuild format). MSBuild also supports >> options that devenv does not (like increased verbosity). Coincidently, the >> switch from devenv to MSBuild has very little to do with .NET and more to >> do with the removal of VCBuild on favour of MSBuild. In anything newer than >> VS2010 devenv just calls MSBuild anyway! >> >> Hope this helps. >> >> -- >> Cinder Roxley >> Sent with Airmail >> >> _______________________________________________ >> 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