Hi,
Which version of CMake are you using?
On Sun, Mar 26, 2017 at 5:01 AM, HarpyWar wrote:
> CMake could not find Visual Studio 2017 and stops with error:
> -- The CXX compiler identification is unknown
>
>
> Initially Visual Studio Community was installed in path:
> E:\Microsoft
> But actually
The latest version cmake-3.8.0-rc3-win32-x86.zip
On Mon, Mar 27, 2017 at 4:04 PM, Robert Maynard
wrote:
> Hi,
>
> Which version of CMake are you using?
>
> On Sun, Mar 26, 2017 at 5:01 AM, HarpyWar wrote:
> > CMake could not find Visual Studio 2017 and stops with error:
> > -- The CXX compiler
I have a build with two or three tools that generate headers and
source files. Getting the source files compiled is easy enough: when
they're mentioned as source files (in add_library or add_executable)
the custom rule gets triggered.
But that doesn't seem to be true for header files included by
n
I just installed the Visual Studio Community 2017 edition into my D
drive and verified that both the 32bit and 64bit compiler was found
correctly.
The C compiler identification is MSVC 19.10.25017.0
The CXX compiler identification is MSVC 19.10.25017.0
Check for working C compiler:
D:/Work/VisualS
On 03/27/2017 09:35 AM, Robert Maynard wrote:
> So the real question is how did your compiler end up in the C drive
> and not the alternative drive like mine. Do you run the visual studio
> installer multiple times?
Did you have any of the VS 15 preview versions installed previously?
For referenc
On 03/26/2017 11:01 AM, HarpyWar wrote:
Output from vswhere.exe shows that Visual Studio is installed on disk C:\
(https://github.com/Microsoft/vswhere)
Perhaps also try:
vswhere -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64
-requires Microsoft.VisualStudio.Component.Window
> On Mar 27, 2017, at 6:31 AM, Bruce Stephens
> wrote:
>
> I have a build with two or three tools that generate headers and
> source files. Getting the source files compiled is easy enough: when
> they're mentioned as source files (in add_library or add_executable)
> the custom rule gets trigge
Yes, that's the idea: I have custom commands (created with
add_custom_command) listing the headers in OUTPUT.
And there are source files which #include such headers.
I'd like it so that compiling such a source file would cause the
header to be generated.
Concretely, with a CMakeLists.txt like th
> On Mar 27, 2017, at 2:57 PM, Bruce Stephens
> wrote:
>
> Yes, that's the idea: I have custom commands (created with
> add_custom_command) listing the headers in OUTPUT.
>
> And there are source files which #include such headers.
>
> I'd like it so that compiling such a source file would cau
