I'm calling msbuild.exe from the Windows\Microsoft.NET\Framework\v3.5\ directory, and still getting these errors, so either I have something set up wrong or MS didn't Iron out all the C++ kinks :(
I can't seem to find anything relevant on the net related to this issue, which makes it all the more frustrating, as I feel I must be doing something wrong that everyone else got right! Anyone successfully managed to get a C++ .sln with multiple projects in it to successfully build with CCNet? Alex, you seem to suggest you have done so - I'm not doing any multicore flag stuff, just a debug build targeted for Windows DirectX. Here's my specific commandline: C:\SVNProject\Project\Source>c:\windows\Microsoft.NET\Framework \v3.5\MSBuild.exe Project.sln /p:Configuration=Debug / p:Platform=DirectX /v:diag I've tried adding various things like "/p:"VCBuildAdditionalOptions=/ useenv" and "/p:ReferencePath=pathtoincludedheaders" etc but none of those things appeared to make any difference. Best regards, Phil On Sep 11, 2:27 am, Alex <[EMAIL PROTECTED]> wrote: > I never really found a working solution for this and ended up giving > up on MsBuild 2.0.5727 with C++ projects. However if you can use > MsBuild 3.5 you will find Microsoft ironed out all the C++ kinks. The > only exception I have found is you can not build 64 bit targets with > the multicore flag. > > On Sep 10, 11:44 am, seffyroff <[EMAIL PROTECTED]> wrote: > > > Hi again guys, > > > I'm attempting to build a C++ project from a .sln which has multiple > > projects in it, using MSBuild. when I try and run MSBuild from teh > > commandline with my sln file, Configuration and Platform settings, it > > errors out because it can't find things like cstdio, d3d9, windows.h > > etc. > > > I've Googled and Googled and Googled and can't seem to find a way to > > give MSBuild Include paths on the commandline. Anybody experienced > > this? Am I approaching this wrong somewhow?
