https://www.incredibuild.com/frequently-asked-questions-technical.html#q4
Q: Can IncrediBuild be used from the command-line or from build scripts?

A: Yes. IncrediBuild includes a strong command-line interface for building
projects, which can easily be integrated in any script that runs
msdev.exe/devenv.exe to build projects. In fact, BuildConsole.exe supports
the devenv/msdev command line syntax so you would typically only need to
replace the executable name in your script!


On Wed, Feb 4, 2015 at 9:30 PM, Nicky Perian <nickyper...@gmail.com> wrote:

> A look at the options below BuildConsole indicated that devenv is the
> underlying builder.
>
> devenv secondlife.sln /build "Release|Win32"
> would be the underlying command as neither of those options can be used
> with MSBuild.
>
>
>             <key>Release</key>
>             <map>
>               <key>build</key>
>               <map>
>                 <key>arguments</key>
>                 <array>
>                   <string>SecondLife.sln</string>
>                 </array>
>                 <key>command</key>
>                 <string>BuildConsole</string>
>                 <key>options</key>
>                 <array>
>                   <string>/build</string>
>                   <string>"/cfg=Release|Win32"</string>
>                 </array>
>               </map>
>               <key>configure</key>
>               <map>
>                 <key>arguments</key>
>                 <array>
>                   <string>..\indra</string>
>                   <string>&amp;&amp;</string>
>                   <string>..\indra\tools\vstool\VSTool.exe</string>
>                   <string>--solution</string>
>                   <string>SecondLife.sln</string>
>                   <string>--config</string>
>                   <string>Release</string>
>                   <string>--startup</string>
>                   <string>secondlife-bin</string>
>                 </array>
>                 <key>options</key>
>                 <array>
>                   <string>-G</string>
>                   <string>"Visual Studio 12"</string>
>                 </array>
>               </map>
>               <key>name</key>
>               <string>Release</string>
>             </map>
>
> On Wed, Feb 4, 2015 at 5:17 PM, Nicky Perian <nickyper...@gmail.com>
> wrote:
>
>> To complete the record as a couple replies  missed the list
>> git pull / merge from singularity 1-20-2015
>> tip at hash 123ded50
>> by Inusaito Sayori 2015-01-20 16:44:22
>> origin https://github.com/singularity-viewer/SingularityViewer.git
>>  (fetch)
>>
>> the msbuild code was put in as an experiment by Shyotl on December 18.
>> 2014
>>
>> https://github.com/singularity-viewer/SingularityViewer/commit/e57bcea3b648bc13ceeb1a5b53a39d27cf103c30
>>
>> I don't know when he actually pushed his branch but I assume it was after
>> 1-20-2015.
>>
>> So it appears that msbuild has only been in use by Singularity for at
>> most 2 weeks.
>>
>> My point is that devenv has been used for a very long time by Singularity
>> with afaik no bad results.
>>
>> So, no my sources were not well out of date and no I did present a self
>> edited code snip.
>>
>>
>>
>>
>> On Wed, Feb 4, 2015 at 4:13 PM, Cinder Roxley <cin...@alchemyviewer.org>
>> wrote:
>>
>>> On February 4, 2015 at 2:18:55 PM, Nicky Perian (nickyper...@gmail.com)
>>> wrote:
>>>
>>> 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)
>>>
>>>
>>> Either you’ve intentionally removed msbuild from this block of code or
>>> your sources are well out of date. -_-
>>>
>>> https://bitbucket.org/lkalif/singularityviewer/src/f0b18e52a3d977c2c19f2a6b4e50292acb5941f2/indra/develop.py?at=master#cl-675
>>>
>>> --
>>> Cinder Roxley
>>> Sent with Airmail
>>>
>>>
>>>         # 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}
>>>
>>>
>>> _______________________________________________
>>> 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

Reply via email to