[Cmake-commits] CMake branch, master, updated. v3.9.2-809-g6b76615

_VERSION_MINOR 9) -set(CMake_VERSION_PATCH 20170914) +set(CMake_VERSION_PATCH 20170915) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Adding compile and build type tests to CMake/CTest

On 9/14/2017 4:45 PM, Bill Hoffman wrote: On 9/12/2017 1:11 PM, Robert Ramey wrote: Could we get some response on Edward's suggestion here? It's a serious obstacle to implementing support of CMake in Boost libraries. I don't think it would be a problem to implement something like this in

Re: [CMake] Adding compile and build type tests to CMake/CTest

On 9/14/2017 4:45 PM, Bill Hoffman wrote: On 9/12/2017 1:11 PM, Robert Ramey wrote: Could we get some response on Edward's suggestion here? It's a serious obstacle to implementing support of CMake in Boost libraries. I don't think it would be a problem to implement something like this in

Re: [cmake-developers] cmake-server protocol versioning

Thank you very much for the information. As I learn more about cmake-server and figure out what we are using on our end I would be happy to contribute tests where it makes sense. It would be great to move cmake-server towards removing the experimental tag. Justin -Original Message-

Re: [cmake-developers] cmake-server protocol versioning

Hi Justin, On Thu, Sep 14, 2017 at 6:52 PM, Justin Goshi via cmake-developers wrote: > I work at Microsoft on the version of CMake shipping with Visual Studio, and > we use the cmake-server to talk to CMake. Cool! > At some point between cmake version 3.9.0 and

Re: [CMake] Adding compile and build type tests to CMake/CTest

On 9/12/2017 1:11 PM, Robert Ramey wrote: Could we get some response on Edward's suggestion here? It's a serious obstacle to implementing support of CMake in Boost libraries. I don't think it would be a problem to implement something like this in CMake. It might make more sense to move this

[Cmake-commits] CMake branch, master, updated. v3.9.2-808-g90b931e

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 90b931e115fa6da965135a3a2160e2efbeac2379 (commit) via

[cmake-developers] cmake-server protocol versioning

I work at Microsoft on the version of CMake shipping with Visual Studio, and we use the cmake-server to talk to CMake. At some point between cmake version 3.9.0 and 3.9.1 the cmake-server protocol changed. Looking through the source code, I see that cmServerProtocol1::ProtocolVersion now

Re: [CMake] Understanding constraint graph cycles

Yes, You most likely want to look at BUILD_RPATH or INSTALL_RPATH depending on if these libraries are located in your build directory or install directory. On Mon, Sep 4, 2017 at 4:39 PM, James Turner wrote: > > On 4 Sep 2017, at 18:37, Robert Maynard

[Cmake-commits] CMake branch, master, updated. v3.9.2-806-g0865a24

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 0865a24fc1c47d75f1381659ba398e6944c9a724 (commit) via

[Cmake-commits] CMake branch, release, updated. v3.9.2-7-gbadc892

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, release has been updated via badc892ff8ea48b499694bc1dc94b5bac272531b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.9.2-793-gfda9a94

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 fda9a94fe6061908e1d66c111f9030baa62cccf7 (commit) via