Hi David,<div> I agree with what you are saying. Just to confirm it I built a series of programs (67 in the solution) that use boost (by using CMake as you describe below) for Visual Studio Express 2010 and 2012 (both 64-bit builds). CMake had no trouble finding the relevant build environment for VS2010 and VS2012. This confirms that CMake works as expected and also there is no need to modify the build environment when using the IDE.</div>
<div> However if you build from a command line using devenv, msbuild or nmake then you will need to set the appropriate environment for VS2010 or VS2012 but I would do this after running the cmake-gui by double-clicking on the icon as David mentions below. </div>
<div> Let CMake set up everything first and then if you want to use a command prompt, use the relevant VS batch file to set up the environment in the command window.</div><div> By the way I think the VS2012 compile is faster then the VS2010 compile, in the above case 45s vs 51s.</div>
<div><br></div><div><br></div><div>Regards</div><div> Andrew</div><div><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>---------- Forwarded message ----------<br>
From: David Cole <<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>><br>To: Michael Jackson <<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>><br>
Cc: "<a href="mailto:cmake@cmake.org" target="_blank">cmake@cmake.org</a> MailingList" <<a href="mailto:cmake@cmake.org" target="_blank">cmake@cmake.org</a>><br>
Date: Wed, 28 Nov 2012 08:17:24 -0500<br>Subject: Re: [CMake] Problem with Visual Studio 2010, Windows 7 64bit<br>You should never allow Visual Studio or CMake installers to make changes to your environment.<div><br></div>
<div>They are unnecessary and cause complications when multiple versions are installed.</div><div><br></div><div>When I use cmake-gui, I double-click an icon on my desktop, or start it from an icon in the start menu. I almost never run it from a Visual Studio command prompt. It's unnecessary...</div>
<div><br></div><div>Visual Studio knows all about its own installation and environment, and so there's no need to allow it to modify your machine's environment. That's what the command prompt shortcuts are for: when you need the environment, you can just run the command prompt with it, and use it as needed. But for typical VS only use, it's never needed.</div>
<div><br></div><div>So: moral of the story from my point of view is: minimize environment changes from all installers... Things should work without environment changes, and if they don't... that's a bug.</div><div>
<br></div><div><br></div><div>2 cents,</div><div>David C.</div><div><br></div><div><br></div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 28, 2012 at 7:59 AM, Michael Jackson <span dir="ltr"><<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br>
On Nov 28, 2012, at 7:37 AM, David Doria <<a href="mailto:daviddoria@gmail.com" target="_blank">daviddoria@gmail.com</a>> wrote:<br>
<br>
> On Wed, Nov 28, 2012 at 4:22 AM, Andrew Maclean<br>
> <<a href="mailto:andrew.amaclean@gmail.com" target="_blank">andrew.amaclean@gmail.com</a>> wrote:<br>
>> Interesting ... I have no problems, the only thing I can think of is that I<br>
>> had VS 2010 SP1 installed before I installed VS 2012 Express, I did not use<br>
>> any of the RC versions.<br>
><br>
> Petr,<br>
><br>
> A colleague mentioned that with the same setup he was getting the same<br>
> error, and then installed SP1 for VS 2010 and things started working.<br>
> It would really be great if there were better checks/errors because it<br>
> is really a huge barrier for projects like VTK to get users to fight<br>
> through install problems. "Hey you should use VTK for that" works when<br>
> they have to follow a few instructions and it works, but when they<br>
> have to spend days working through cryptic errors most tend to give up<br>
> and then we lose a user.<br>
><br>
> Andrew,<br>
><br>
> I'm almost certain that it will never work using the VS generators<br>
> (with very different "can't find the compiler type of errors") unless<br>
> you run cmake-gui from a terminal unless you have manually added many<br>
> VS things to the system environment variables. At least that has been<br>
> my experience on many machines.<br>
><br>
> David<br>
> --<br>
<br>
<br>
</div>Here is my theory on mixing visual studios. When you install Visual Studio Windows will dutifully add the Visual Studio tools to the PATH for everyone. This is why you can just launch CMakeGui and have the Visual Studio generators work correctly. All is well. This is where I ran into problems.. Now install Visual Studio 2012 (or any other version) alonside VS2010 and Windows will again the 2012 to the PATH also. Now you have BOTH VS version's tools in the path but what ever is found FIRST is the one that is going to be used which will cause problems when launching CMakeGUi from Windows Explorer. At least this is what I saw years ago and why I NEVER mix versions. I install each version into its own Virtual Machine and run that way. It avoids all of these PATH issues.<br>
Unless CMake has some code to look into the registry to fully determine which compiler you want and setup the environment correctly by removing PATHS from a version of Visual Studio that you are NOT using I don't see how having more than a single Visual studio installed is going to work***<br>
<br>
<br>
*** It can work if you go into the "Environment Variables" for Windows and REMOVE any and all references to Visual Studio. Then when you want to configure a project you launch a "Visual Studio Command Prompt" or "Visual Studio x64 Command Prompt" and then launch CMake-gui from there which will properly setup the environment for you and the generator will work correctly every time because there is no mixing of paths. This is how I do it. Yes it is a few extra clicks and some typing but it avoids days of fighting hidden path issues.<br>
<br>
Of course I could be wrong on most of the above but it works for me for the last 3 years so I am not about to change. Just my nickels worth of advice.<br>
___________________________________________________________<br>
Mike Jackson Principal Software Engineer<br>
BlueQuartz Software Dayton, Ohio<br>
<a href="mailto:mike.jackson@bluequartz.net" target="_blank">mike.jackson@bluequartz.net</a> <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
<div><div><br>
--<br>
<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br></div>
<br><br></blockquote></div>-- <br>___________________________________________<br>Andrew J. P. Maclean<br><br>___________________________________________<br>
</div>