I will probably complain from now until it's fixed with a perference (which will probably mean me writing a patch; but... )
Devenv has a side effect that msbuild does not; devenv writes to the most recently used projects, msbuild does not. So I can keep using visual studio to build my other c# projects that I work on, and even have references to them in most recently used. I have added to my toplevel cmakes a check for msbuild to set that before the cmake default script checks; but this doesn't fix the CMAKE_TRY_COMPILE.sln that's used by cmake itself; so running a series of builds ends up basically obliterating the most recently used files with CMAKE_TRY_COMPILE's. On Fri, Jun 1, 2012 at 3:49 PM, J Decker <d3c...@gmail.com> wrote: > shouldn't cmake use 'msbuild' instead of 'devenv.com' or 'devenv.exe'? > > I have a feeling that would solve one of my issues with visual studio, > in that after building a long chain of cmake projects using visual > studio, all of the most recent project references are updated to being > the projects that were built, thereby losing the projects I'm actually > working on. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
