Correct, this is one of the concerns that makes it more complex than just searching for the first vcvarsall.bat you come to.
I'd like to match up the vcvarsall to the version of visual studio currently in use by CMake. I think there are now enough pieces that I can write a CMake 'FindVSEnvironment.cmake'. While I can't test it for a large number of MSVC versions, I'll post it and hopefully others can help out. Rob On Thu, Jan 9, 2014 at 6:44 AM, John Drescher <[email protected]> wrote: > > Why not just write your own batch ('buildit.bat') file that does: > > > > call vcvarsall.bat > > nmake > > > > (or whatever the command to build in the VS command prompt is...) > > > > And then your command to build is: > > > > C:/full/path/to/buildit.bat > > > > It's presumably in a Windows-specific chunk of your CMakeLists anyway, so > > that should work fairly simply. > > I think the part of problem would be figuring out what vcvarsall.bat > to run especially if you have more than 1 version of Visual Studio. > > John >
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
