[CMake] FW: Visual Studio 2017
Randy Heiland
randy.heiland at gmail.com
Tue Sep 19 11:51:31 EDT 2017
I failed to send my previous reply to the list - see below for that. This
is a follow-on, using the repo mentioned previously.
--- Attempt #1
# Pointing out that my Command Prompt shell doesn't need to know about
the 'cl' compiler, in order to run cmake:
C:\Users\Owner\dev\cmake_learn\cmake_learn-master\build>cl
'cl' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Owner\dev\cmake_learn\cmake_learn-master\build>cmake ..
-- Building for: Visual Studio 15 2017
-- The C compiler identification is MSVC 19.11.25508.2
-- The CXX compiler identification is MSVC 19.11.25508.2
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/x86/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/x86/cl.exe --
works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/x86/cl.exe
-- Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual
Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/x86/cl.exe --
works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found OpenMP_C: -openmp (found version "2.0")
-- Found OpenMP_CXX: -openmp (found version "2.0")
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/Owner/dev/cmake_learn
/cmake_learn-master/build
This successfully builds the following files, but no Makefile so that I can
simply run 'nmake' from the command line:
d----- 9/19/2017 10:26 AM BioFVM
d----- 9/19/2017 10:26 AM CMakeFiles
d----- 9/19/2017 10:26 AM core
d----- 9/19/2017 10:26 AM custom_modules
d----- 9/19/2017 10:26 AM modules
-a---- 9/19/2017 10:26 AM 62588 ALL_BUILD.vcxproj
-a---- 9/19/2017 10:26 AM 304 ALL_BUILD.vcxproj.filters
-a---- 9/19/2017 10:26 AM 14371 CMakeCache.txt
-a---- 9/19/2017 10:26 AM 1841 cmake_install.cmake
-a---- 9/19/2017 10:26 AM 7860 PhysiCell.sln
-a---- 9/19/2017 10:26 AM 76341 PhysiCell.vcxproj
-a---- 9/19/2017 10:26 AM 611 PhysiCell.vcxproj.filters
-a---- 9/19/2017 10:26 AM 274 PhysiCellConfig.h
-a---- 9/19/2017 10:26 AM 46027 ZERO_CHECK.vcxproj
-a---- 9/19/2017 10:26 AM 547 ZERO_CHECK.vcxproj.filters
--------------------------------
--- Attempt #2 (without invoking vcvarsall.bat; rf.
https://dmerej.info/blog/post/cmake-visual-studio-and-the-command-line/ )
C:\Users\Owner\dev\cmake_learn\cmake_learn-master\build>cmake -G"NMake
Makefiles" ..
-- The C compiler identification is unknown
-- The CXX compiler identification is unknown
CMake Error at CMakeLists.txt:5 (project):
The CMAKE_C_COMPILER:
cl
is not a full path and was not found in the PATH.
To use the NMake generator with Visual C++, cmake must be run from a shell
that can use the compiler cl from the command line. This environment is
unable to invoke the cl compiler. To fix this problem, run cmake from the
Visual Studio Command Prompt (vcvarsall.bat).
Tell CMake where to find the compiler by setting either the environment
variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path
to
the compiler, or to the compiler name if it is in the PATH.
--------------------------------
--- Attempt #3 (after invoking the vcvarsall.bat, thereby making my shell
aware of the 'cl' compiler)
C:\Users\Owner\dev\cmake_learn\cmake_learn-master\build>cmake -G"NMake
Makefiles" ..
... successfully runs ...
Generates the following files, including a Makefile:
d----- 9/19/2017 10:46 AM BioFVM
d----- 9/19/2017 10:45 AM CMakeFiles
d----- 9/19/2017 10:45 AM core
d----- 9/19/2017 10:46 AM custom_modules
d----- 9/19/2017 10:46 AM modules
-a---- 9/19/2017 10:44 AM 15307 CMakeCache.txt
-a---- 9/19/2017 10:44 AM 1839 cmake_install.cmake
-a---- 9/19/2017 10:44 AM 7562 Makefile
-a---- 9/19/2017 10:46 AM 1503232 PhysiCell.pdb
-a---- 9/19/2017 10:44 AM 274 PhysiCellConfig.h
PS C:\Users\Owner\dev\cmake_learn\cmake_learn-master\build> nmake
Microsoft (R) Program Maintenance Utility Version 14.11.25508.2
... builds most of the way OK ...
... (but currently get an error at the end, trying to build code in my
'cmake_learn' repo)
-Randy
On Mon, Sep 18, 2017 at 10:22 PM, Randy Heiland <randy.heiland at gmail.com>
wrote:
> Thanks everyone for your replies! I continue to learn/play, but still have
> problems it seems. I've created a repo, in case anyone would be willing to
> show me the error of my ways:
> https://github.com/rheiland/cmake_learn
>
> On Win10, I too *seem* to have to run the vcvarsall.bat to have things
> (sort of) work.
>
> I'm using cmake 3.9.2.
>
> -Randy
>
>
> On Mon, Sep 18, 2017 at 1:57 PM, Robert Maynard <
> robert.maynard at kitware.com> wrote:
>
>> From a default cmd.exe I see cmake 3.9 correctly finding VS2017 when
>> specifying the VS Generator.
>>
>> C:\test\build>C:\support\cmake-3.9.2\bin\cmake -G "Visual Studio 15
>> 2017" ../src
>> -- The C compiler identification is MSVC 19.11.25508.2
>> -- The CXX compiler identification is MSVC 19.11.25508.2
>> -- Check for working C compiler: C:/Program Files (x86)/Microsoft
>> Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/
>> x86/cl.exe
>> -- Check for working C compiler: C:/Program Files (x86)/Microsoft
>> Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/
>> x86/cl.exe
>> -- works
>> -- Detecting C compiler ABI info
>> -- Detecting C compiler ABI info - done
>> -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft
>> Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/
>> x86/cl.exe
>> -- Check for working CXX compiler: C:/Program Files (x86)/Microsoft
>> Visual Studio/2017/Community/VC/Tools/MSVC/14.11.25503/bin/HostX86/
>> x86/cl.exe
>> -- works
>> -- Detecting CXX compiler ABI info
>> -- Detecting CXX compiler ABI info - done
>> -- Detecting CXX compile features
>> -- Detecting CXX compile features - done
>> -- Configuring done
>> -- Generating done
>> -- Build files have been written to: C:/test/build
>>
>> On Mon, Sep 18, 2017 at 10:49 AM, Thompson, KT <kgt at lanl.gov> wrote:
>> > Robert,
>> >
>> > That certainly doesn't work for me - but maybe I'm doing something
>> non-standard.
>> >
>> > If I don't source the vcvarsall.bat file, SDK installations (c:\Program
>> Files (x86)\Windows Kits\... and c:\Program Files (x86)\Microsoft SDKs\...)
>> are not found by CMake.
>> >
>> > -kt
>> >
>> > -----Original Message-----
>> > From: Robert Maynard [mailto:robert.maynard at kitware.com]
>> > Sent: Monday, September 18, 2017 8:17 AM
>> > To: Thompson, KT <kgt at lanl.gov>
>> > Cc: cmake at cmake.org
>> > Subject: Re: [CMake] FW: Visual Studio 2017
>> >
>> > You shouldn't need to import VS17 vcvarsall to use the VS17 Generator,
>> > that should only be needed if using the MSYS or Ninja generators.
>> >
>> > As far as building from the command line, the easiest route is to use
>> > cmake --build <path to build directory> --config <cfg>
>> >
>> > On Fri, Sep 15, 2017 at 3:05 PM, Thompson, KT <kgt at lanl.gov> wrote:
>> >> Randy,
>> >>
>> >> Miroslav's recommendation should work. To expand on his response, here
>> are the commands that I use with VS2017 to allow cmake to run from the
>> command line:
>> >>
>> >> - Start cmd session (should also work via powershell)
>> >> - To import VS17's command line environment run "C:\Program Files
>> (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat"
>> x86
>> >> - Add extra project specific environment variables (possibly including
>> appending PATH with the location of cmake).
>> >>
>> >> I created a batch file that does these steps for me (and a shortcut on
>> my desktop that runs the batch file).
>> >>
>> >> @echo off
>> >> rem cmake-with-vs17-env.bat
>> >> @call "C:\Program Files (x86)\Microsoft Visual
>> Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" x86 %*
>> >> set PATH=%PATH%;c:\MinGW\bin;C:\Program Files\CMake\bin;C:\Program
>> Files\doxygen\bin;c:\Python27amd64
>> >> rem set CMAKE_PREFIX_PATH=<whatever>
>> >>
>> >> With this environment, I can run cmake from the command line
>> (cmake-gui or cmake). I can generate "Visual Studio 15 2017" or "MSYS
>> Makefiles" projects and I can build them with or w/o the GUI.
>> >>
>> >> I hope this helps!
>> >>
>> >> -kt
>> >>
>> >>
>> >> -----Original Message-----
>> >> From: CMake [mailto:cmake-bounces at cmake.org] On Behalf Of Mateju
>> Miroslav, Ing.
>> >> Sent: Friday, September 15, 2017 6:15 AM
>> >> To: Randy Heiland <randy.heiland at gmail.com>; cmake at cmake.org
>> >> Subject: Re: [CMake] Visual Studio 2017
>> >>
>> >> Hello Randy,
>> >>
>> >> From: CMake [mailto:cmake-bounces at cmake.org] On Behalf Of Randy
>> Heiland
>> >> Sent: Friday, September 15, 2017 1:38 PM
>> >>
>> >>> Is there a "best way" to use cmake for VS17 (but same cakelists for
>> Linux)? And by "best", I mean with minimal effort on users.
>> >>> To be more specific, on Windows, I *think* I'd like to have users
>> install the cmake binary, then use Powershell to build an application.
>> >> Is there really a need for using PowerShell if you also want to use
>> the same CMakeLists for Linux?
>> >>
>> >>> But my initial attempt to do so is confusing. I install VS17 (for
>> C++), it installs in standard path, but 'cl' is not found in Powershell. I
>> read that I shouldn't edit my PATH (nor do I really want users to have to),
>> but run some .bat instead to setup my env. So, how should one specify the
>> compiler for cmake? Oh yes, then I see that VS17 also has its own cmake??
>> >>
>> >>
>> >> Have you run CMake successfully yet? I am not really aware how it
>> works but CMake *can* for sure detect VS in my CLI environment without
>> having VS in PATH. If you use an IDE that understands CMake (like VS17 or
>> Qt Creator, for example), you should be able to open a CMake project in the
>> IDE and build it there. Please report your particular problem if it does
>> not work for you.
>> >> If you prefer to run cl.exe in CLI, then vcvarsall.bat is the .bat
>> file you are looking for.
>> >>
>> >> Best regards,
>> >>
>> >> Ing. Miroslav Matějů
>> >> Programmer Analyst
>> >>
>> >> AŽD Praha s.r.o.
>> >> Technology Division
>> >> Research and Development
>> >> Žirovnická 2/3146, 106 17 Prague
>> >> Czech Republic
>> >> Phone: +420 267 287 476 <+420%20267%20287%20476>
>> >> Web: www.azd.cz
>> >> --
>> >>
>> >> 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://public.kitware.com/mailman/listinfo/cmake
>> >> --
>> >>
>> >> 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://public.kitware.com/mailman/listinfo/cmake
>> --
>>
>> 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://public.kitware.com/mailman/listinfo/cmake
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20170919/7e1e7423/attachment-0001.html>
More information about the CMake
mailing list