Re: [CMake] Handling generated headers

> 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)

Re: [CMake] Handling generated headers

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

Re: [CMake] Handling generated headers

> 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

Re: [CMake] Visual Studio 2017 could not be found if installed in non-default location

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: >

[CMake] Handling generated headers

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

Re: [CMake] Visual Studio 2017 could not be found if installed in non-default location

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

Re: [CMake] Visual Studio 2017 could not be found if installed in non-default location

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:

Re: [CMake] Visual Studio 2017 could not be found if installed in non-default location

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

Re: [CMake] Visual Studio 2017 could not be found if installed in non-default location

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-586-gb645aac

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated discards 66839d5a04010d8b42eefdc5a9a1e349816d4c85 (commit) discards

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-588-gc7df2fb

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via c7df2fb6528c884ec69bedce2a4595997adc72ac (commit) via

Re: [cmake-developers] Build multiple CMake projects

Hi Jerry, from your description, it seems like you might be looking for the CMake module ExternalProject: https://cmake.org/cmake/help/latest/module/ExternalProject.html The idea is that you create a "superbuild" CMake project which consists of ExternalProject_Add calls and related

Re: [cmake-developers] Build multiple CMake projects

On Fri, Mar 24, 2017 at 7:35 PM, wrote: > Hi, > > I have some CMake projects which depend on each other. They provide Config > scripts (all generated with the help of CMakePackageConfigHelpers) and the > CMake projects find there dependencies with find_package(). Even the >

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-590-gc4c307b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated via c4c307b8259c39737019ddd1b7d7ce4b5cf89c15 (commit) via

[cmake-developers] Support for version suffixes

Hi folks, I'd like to bring this issue to your attention to canvas some feedback regarding the use of version suffixes: https://gitlab.kitware.com/cmake/cmake/issues/16716 This is basically a proposal to allow an optional version suffix like "-rc3", "-beta1" etc. in addition to the

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-584-g7f81bb1

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated discards d46bcf677806ecc9e7116bd88b3f51954e301e8e (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-575-gba37985

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via ba3798555d7e018ddd384f6990645a8407893f54 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-582-g89e2c92

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 89e2c92f546c3d1b702b2c0ca206eabfc3f7caab (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-584-g66839d5

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated discards 7f81bb18196077678fb6b05114208bf4ab328a05 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-583-g2149943

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 21499431e05b0defb134b10b1753488c0516bafd (commit) from

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-591-g23929b1

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, next has been updated discards c4c307b8259c39737019ddd1b7d7ce4b5cf89c15 (commit) discards

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc3-582-g89e2c92

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, nightly-master has been updated via 89e2c92f546c3d1b702b2c0ca206eabfc3f7caab (commit) via

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc3-590-gc4c307b

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, nightly has been updated discards ec5a687ebe40567ad8217ab29ba2e5a25ac4a71b (commit) discards