Search Results

Search found 6 results on 1 pages for 'vcbuild'.

Page 1/1 | 1 

• .net framework sdk version(csc.exe) using vcbuild.exe on the command line.

  - by r9r9r9

  I create a c# class library project named: testVcBuild, then use vcbuild.exe to build the project in the command line like: C:\Program Files\Microsoft Visual Studio 9.0\VC\vcpackages>vcbuild testVcBuild.csproj "Debug|Win32" the out put shows: Microsoft (R) Visual C++ Project Builder - Command Line Version 9.00.21022 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft (R) Build Engine Version 2.0.50727.4927 [Microsoft .NET Framework, Version 2.0.50727.4927] Copyright (C) Microsoft Corporation 2005. All rights reserved. I found that the vcbuild.exe always call the "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig .." the problem is how can I change the Framework version to v3.5? I found my project works fine with the v3.5 but it's broken in the v2.0.50727. I try to use msbuild.exe instead of vcbuild.exe, everything goes well, I just don't understand how can I make it with the vcbuild.exe? win7+vs2005+vs2008 installed.

  Read the article

• how to specify the Build Engine Version when using VcBuild.exe on the command line.

  - by r9r9r9

  I create a c# class library project named: testVcBuild, then use vcbuild.exe to build the project in the command line like: C:\Program Files\Microsoft Visual Studio 9.0\VC\vcpackages>vcbuild testVcBuild.csproj "Debug|Win32" the out put shows: Microsoft (R) Visual C++ Project Builder - Command Line Version 9.00.21022 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft (R) Build Engine Version 2.0.50727.4927 [Microsoft .NET Framework, Version 2.0.50727.4927] Copyright (C) Microsoft Corporation 2005. All rights reserved. I found that the vcbuild.exe always call the "C:\Windows\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig .." the problem is how can I change the Framework version to v3.5? I found my project works fine with the v3.5 but it's broken in the v2.0.50727. I try to use msbuild.exe instead of vcbuild.exe, everything goes well, I just don't understand how can I make it with the vcbuild.exe? win7+vs2005+vs2008 installed.

  Read the article

• conditionals for C++ using MSBuild/vsbuild?

  - by redtuna

  I have a C++ project in Visual Studio 2008 and I'd like to be able to compile several versions from the command line, defining conditional variables (aka #define). If it were just a single file to compile I'd use something like cl /D, but this is complex enough that I would like to be able to use VS's other features like the build order etc. I've seen a similar question asked in stackoverflow and the answer was to use /p:DefineConstants="var1;var2". This doesn't seem to work with C++ though. The other problem with that answer is that it replaces the conditional variables, instead of adding to them. The vcproj files for C++ look quite different. If msbuild (or vsbuild) had a way to change Configurations/Tool[name="VCCLCompilerTool"] we'd be golden. But I haven't found such an option. The vcproj files are under source control so I'd rather not have a script mess with them. I've considered doubling the number of configurations (one with the #define, one without). That'd be annoying, and I'm especially unhappy with having to modify these configurations in tandem every time I need to modify anything there. A previous similar question found no solution. I'm hoping that has changed since? How would you go about building those variants (with and without define) from the command line? Thanks!

  Read the article

• Scala isn't allowing me to execute a batch file whose path contains spaces.Same Java code does.What

  - by Geo

  Here's the code I have: var commandsBuffer = List[String]() commandsBuffer ::= "cmd.exe" commandsBuffer ::= "/c" commandsBuffer ::= '"'+vcVarsAll.getAbsolutePath+'"' commandsBuffer ::= "&&" otherCommands.foreach(c => commandsBuffer ::= c) val asArray = commandsBuffer.reverse.toArray val processOutput = processutils.Proc.executeCommand(asArray,true) return processOutput otherCommands is an Array[String], containing the following elements: vcbuild /rebuild path to a .sln file vcVarsAll contains the path to Visual Studio's vcvarsall.bat. It's path is C:\tools\microsoft visual studio 2005\vc\vcvarsall.bat. The error I receive is: 'c:\Tools\Microsoft' is not recognized as an internal or external command, operable program or batch file.. The processutils.Proc.executeCommand has the following implementation: def executeCommand(params:Array[String],display:Boolean):(String,String) = { val process = java.lang.Runtime.getRuntime.exec(params) val outStream = process.getInputStream val errStream = process.getErrorStream ... } The same code, executed from Java/Groovy works. What am I doing wrong?

  Read the article

• How to use a specific Windows SDK with MSBuild?

  - by Mac

  I have a large project made of many C++ and C# projects, and a MSBuild (3.5) script to build the whole thing. This script is based on the VCBuild (C++ projects) and MSBuild (C# projects) tasks. It is regularly executed by a Continuous Integration server. I want to be able to select a specific Windows SDK (v6.0A, v7.0, v7.1...) to be used for compilation. As I have many branches in my repository that would ultimately need a different SDK version, I need a way to select the right one before each compilation. On my computer, I have been able to setup a batch script that calls the right SetEnv.cmd before launching the MSBuild script. But this solution is not usable on the CI server as the MSBuild script is executed directly. Do you know of a way to achieve the equivalent of SetEnv.cmd under MSBuild?

  Read the article

• Producing 64-bit builds on Windows with free software

  - by pauldoo

  Hi, I have a C++ project that I've been developing in Microsoft Visual C++ 2008 Express Edition. It has come to the point that I'd like to port to 64-bit and continue development. What is the best way to do this using free software? My thoughts so far: The Express Edition of MSVC doesn't come with 64-bit compilers, so I can install the Windows SDK to get these. I could then port my project files to nmake, and use the IDE just as a tool to debug and invoke my nmake scripts.. The downside to this is that nmake looks very poor. The example towards the end of this tutorial suggests that nmake cannot figure out source file dependences itself, and I don't know of anything equivelant to gcc -M that I could use. Another option might be to use vcbuild from the Windows SDK to produce 64-bit builds from my existing vcproj files. Preliminary investigations show that this doesn't really work, as my project files don't have the 64-bit configurations present. (Perhaps I could fudge this by adding the 64-bit configurations to the vcproj files in a text editor.) A final option might be to give up on MSVC, and port my project to the MinGW/MSYS toolchain.

  Read the article

1