I just tried this on a remote machine with the compiler and can confirm what John is seeing. That said. If you run msbuild on the top level solution you get a slightly more informative error.<div><br></div><div><div>c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1>msbuild Console1.sln</div>
<div>Microsoft (R) Build Engine Version 3.5.30729.1</div><div>[Microsoft .NET Framework, Version 2.0.50727.4206]</div><div>Copyright (C) Microsoft Corporation 2007. All rights reserved.</div><div><br></div><div>Build started 3/7/2011 10:10:25 AM.</div>
<div>Project "c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln" on node 0 (default targets).</div><div> Building solution configuration "Debug|Win32".</div><div>c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln.cache : warning MSB4078: The project file "Console1\Console1.vfproj" is not supported</div>
<div>by MSBuild and cannot be built.</div><div>Done Building Project "c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln" (default targets).</div><div><br></div><div><br></div><div>Build succeeded.</div>
<div><br></div><div>"c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln" (default target) (1) -></div><div>(Console1 target) -></div><div> c:\Users\kitware\Documents\Visual Studio 2010\Projects\Console1\Console1.sln.cache : warning MSB4078: The project file "Console1\Console1.vfproj" is not supporte</div>
<div>d by MSBuild and cannot be built.</div><div><br></div><div> 1 Warning(s)</div><div> 0 Error(s)</div><div><br></div><div>Time Elapsed 00:00:00.01</div></div><div><br><br><div class="gmail_quote">On Mon, Mar 7, 2011 at 9:42 AM, Bill Hoffman <span dir="ltr"><<a href="mailto:bill.hoffman@kitware.com" target="_blank">bill.hoffman@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Mon, Mar 7, 2011 at 9:17 AM, Biddiscombe, John A. <<a href="mailto:biddisco@cscs.ch" target="_blank">biddisco@cscs.ch</a>> wrote:<br>
> Bill<br>
><br>
>> What if you run DevEnv.exe from the command line with the /Upgrade on<br>
>> the vfproj file? Does it change it? Does it work with MSBuild after?<br>
><br>
> No change. Still fails.<br>
><br>
>><a href="http://software.intel.com/en-us/forums/showthread.php?t=81140" target="_blank">http://software.intel.com/en-us/forums/showthread.php?t=81140</a><br>
>>This is explained in the release notes for the Fortran compiler.<br>
>>Please read the section on VS2010.."<br>
><br>
> yes I found this report - unfortunately it does not tell us anything useful. It deals with dependencies, which is different from our problem. I checked to see the the ALL_BUILD project was referencing the cmTryComile, (and it is), but changing this makes no difference - when running msbuild.exe we only treat the cmtrycompile and deleting all the other stuff doesn't solve anything.<br>
><br>
> I'll file a bug report with intel and for now, use makefiles to kick off the generator and then switch.- could we not just use nmake always for the compiler detection step?<br>
<br>
</div>When you file the report, do not include any mention of CMake. I<br>
would just tell them that you did this:<br>
<br>
1. create a new hello world application with the IDE<br>
2. run msbuild on the application<br>
3. you get an error<br>
<br>
We can not use nmake to kick off the generator, it would not even be<br>
testing the same setup that the generator is creating. Might as well<br>
disable all try-compiles because it would not even be testing what the<br>
user would be seeing during the real build.... We might be able to<br>
use devenv /build, however in earlier versions of VS 2010 using devenv<br>
for running the tests of CMake caused devenv to crash multiple<br>
times...<br>
<font color="#888888"><br>
<br>
-Bill<br>
</font><div><div></div><div><br>
><br>
> JB<br>
><br>
> snippet from release notes below<br>
><br>
> 3.6.2 Adjusting Project Dependencies<br>
> If you are converting a project from an earlier version of Visual Studio and had established<br>
> Project Dependencies, these are converted to References by Visual Studio 2010. A Fortran<br>
> project that is referenced by a C/C++ project will prevent the C/C++ project from building, with<br>
> an MSB4075 error. To solve this:<br>
> 1. Right click on the C/C++ project and select References.<br>
> 2. If any Fortran project is shown as a reference, click Remove Reference. Repeat this for<br>
> all Fortran projects shown as a reference. Click OK.<br>
> 3. Repeat the above steps for any other C/C++ project<br>
> Now you have to reestablish project dependencies.<br>
> 1. Right click on the C/C++ project and select Project Dependencies.<br>
> 2. Check the box for each project that is a dependent of this project.<br>
> 3. Click OK.<br>
> 4. Repeat the above steps for any other C/C++ project that has dependencies.<br>
> Unlike earlier versions of Visual Studio, Visual Studio 2010 does not automatically link in the<br>
> output library of dependent projects, so you will need to add those libraries explicitly to the<br>
> parent project under Linker > Additional Dependencies. You can use the Visual Studio macros<br>
> $(ConfigurationName) and $(PlatformName) as required to qualify the path. For example:<br>
> ..\FLIB\$(ConfigurationName)\FLIB.lib<br>
> Where $(ConfigurationName) will expand to Release or Debug, as appropriate. Similarly,<br>
> $(PlatformName) will expand to Win32 or x64 as appropriate.<br>
><br>
_______________________________________________<br>
cmake-developers mailing list<br>
<a href="mailto:cmake-developers@cmake.org" target="_blank">cmake-developers@cmake.org</a><br>
<a href="http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers</a><br>
</div></div></blockquote></div><br>
</div>