/MSVC/14.11.25503/bin/HostX86/x86/cl.exe
>Winsock found at C:/Program Files (x86)/Windows
>Kits/10/Lib/10.0.15063.0/um/x86/WSock32.Lib
>-- Configuring done
>-- Generating done
>
>----
>
>Thanks for your feedback!
>
>-kt
>
>-Origina
- Generating done
Thanks for your feedback!
-kt
-Original Message-
From: Robert Maynard [mailto:robert.mayn...@kitware.com]
Sent: Monday, September 18, 2017 11:58 AM
To: Thompson, KT
Cc: cmake@cmake.org
Subject: Re: [CMake] FW: Visual Studio 2017
From
While the preshing article on CMake is really good, it didn't clearly
cover the fact that Visual Studio projects generated by CMake can be
built from the command line using cmake --build --config <
Release/Debug/... >
On Tue, Sep 19, 2017 at 4:44 PM, Randy Heiland wrote:
> What I'm finding onlin
What I'm finding online so far seems to indicate that one would need to
open the Visual Studio app in order to do something with the .sln. Is that
true? If so, it's not really desirable... well, maybe it is for some users,
but, in general, I'd like to provide a command line solution. Is that
possib
Am 19. September 2017 22:05:36 MESZ schrieb Randy Heiland
:
>I'd love to learn more about this option, assuming it's a simple
>workflow
>via the command line. If there's a writeup related to cmake, would
>welcome
>a pointer. If you can't tell, I'm not really a Windows guy; I'm just
>trying
>to s
I'd love to learn more about this option, assuming it's a simple workflow
via the command line. If there's a writeup related to cmake, would welcome
a pointer. If you can't tell, I'm not really a Windows guy; I'm just trying
to support that community. Hopefully what you're describing would not
requ
Am 19. September 2017 17:51:31 MESZ schrieb Randy Heiland
:
>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' c
t;> > 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 File
(x86)\Windows Kits\... and c:\Program Files (x86)\Microsoft SDKs\...) are not
> found by CMake.
>
> -kt
>
> -Original Message-
> From: Robert Maynard [mailto:robert.mayn...@kitware.com]
> Sent: Monday, September 18, 2017 8:17 AM
> To: Thompson, KT
> Cc: cmake@cmake
riginal Message-
From: Robert Maynard [mailto:robert.mayn...@kitware.com]
Sent: Monday, September 18, 2017 8:17 AM
To: Thompson, KT
Cc: cmake@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 need
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 --config
On Fri, Sep 15, 2017 at 3:05 PM, Thompson, KT wrote:
> Randy,
>
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)\Micros
12 matches
Mail list logo