[CMake] Fwd: Visual Studio command line from CMake

Robert Maynard robert.maynard at kitware.com
Thu Jan 9 10:18:43 EST 2014


Each Visual Studio sets a environment variable that helps you locate the
installed location. So for Visual Studio 2008 it is VS90COMNTOOLS, and for
Visual Studio 2010 it is
VS100COMNTOOLS. So you can have a single bat file that is configured by
cmake to determine both the correct env variable to use, and the proper
args to pass to vcvarsall.bat.



On Thu, Jan 9, 2014 at 9:44 AM, John Drescher <drescherjm at gmail.com> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20140109/e54e50c8/attachment.htm>


More information about the CMake mailing list