[Cmake-commits] CMake branch, master, updated. v3.6.0-rc4-292-gf408a5b

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

[cmake-developers] [PATCH] Improve encoding handling on Windows

On Windows getenv uses ANSI codepage so it needs to be encoded to internally used encoding (eg. UTF-8). Here we use _wgetenv instead and encode that. Also typically Windows applications (eg. MSVC compiler) use current console's codepage for output to pipes so we need to encode that to internally

Re: [cmake-developers] [patch] Document -H and -B

I don't understand the harm of documenting the options and making them public. Brad can you explain? I have worked with numerous colleagues who use them. So far nothing bad happened to them! Seems to me that they are a) used b) useful c) safe Is there context I am missing? Dave On 1 Jul 2016

Re: [cmake-developers] [patch] Document -H and -B

On 01-Jul-16 00:14, Shawn Waldon wrote: On Thu, Jun 30, 2016 at 5:10 PM, Ruslan Baratov > wrote: On 30-Jun-16 23:57, Shawn Waldon wrote: On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote: On 30-Jun-16 23:40, Brad

Re: [cmake-developers] [patch] Document -H and -B

On 01-Jul-16 00:02, Brad King wrote: On 06/30/2016 04:57 PM, Shawn Waldon wrote: mkdir -p "$build" && pushd "$build" && cmake "$src" && popd Or use a ()-enclosed subshell: (mkdir -p "$build" && cd "$build" && cmake "$src") -Brad Okay, this one seems to work. Also you haven't show how

Re: [cmake-developers] [patch] Document -H and -B

On Thu, Jun 30, 2016 at 5:10 PM, Ruslan Baratov wrote: > On 30-Jun-16 23:57, Shawn Waldon wrote: > > On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote: > >> On 30-Jun-16 23:40, Brad King wrote: >> >>> On 06/30/2016 04:28 PM, Ruslan Baratov wrote: >>> On

Re: [cmake-developers] [patch] Document -H and -B

On 30-Jun-16 23:57, Shawn Waldon wrote: On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote: On 30-Jun-16 23:40, Brad King wrote: On 06/30/2016 04:28 PM, Ruslan Baratov wrote: On 30-Jun-16 23:18, Brad King wrote: On 06/30/2016 03:56 PM, Ruslan Baratov

Re: [cmake-developers] [patch] Document -H and -B

On 06/30/2016 04:57 PM, Shawn Waldon wrote: > mkdir -p "$build" && pushd "$build" && cmake "$src" && popd Or use a ()-enclosed subshell: (mkdir -p "$build" && cd "$build" && cmake "$src") -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [cmake-developers] [patch] Document -H and -B

On Thu, Jun 30, 2016 at 4:54 PM, Ruslan Baratovwrote: > On 30-Jun-16 23:40, Brad King wrote: > >> On 06/30/2016 04:28 PM, Ruslan Baratov wrote: >> >>> On 30-Jun-16 23:18, Brad King wrote: >>> On 06/30/2016 03:56 PM, Ruslan Baratov wrote: > What is the public-use way to specify

Re: [cmake-developers] [patch] Document -H and -B

Am Donnerstag, 30. Juni 2016, 23:54:42 schrieb Ruslan Baratov via cmake- developers: > On 30-Jun-16 23:40, Brad King wrote: > > On 06/30/2016 04:28 PM, Ruslan Baratov wrote: > >> On 30-Jun-16 23:18, Brad King wrote: > >>> On 06/30/2016 03:56 PM, Ruslan Baratov wrote: > What is the public-use

Re: [cmake-developers] [patch] Document -H and -B

On 30-Jun-16 23:40, Brad King wrote: On 06/30/2016 04:28 PM, Ruslan Baratov wrote: On 30-Jun-16 23:18, Brad King wrote: On 06/30/2016 03:56 PM, Ruslan Baratov wrote: What is the public-use way to specify source-tree and build-tree by cmake options simultaneously? cd $build && cmake $src

Re: [CMake] CMAKE_C_COMPILE_OBJECT vs

Hi Robert, Yes, we are adding the Keil C8051 compiler, which is very old and uses a very unique command line syntax compared to the others supported by CMake. Also, it's Windows only but Wine works -- so we optionally add Wine on non-Windows platforms. An example would be: wine C51.exe

Re: [cmake-developers] [patch] Document -H and -B

On 06/30/2016 04:28 PM, Ruslan Baratov wrote: > On 30-Jun-16 23:18, Brad King wrote: >> On 06/30/2016 03:56 PM, Ruslan Baratov wrote: >>> What is the public-use way to specify source-tree and build-tree by >>> cmake options simultaneously? >> cd $build && cmake $src > > Will not work if $build

Re: [cmake-developers] [patch] Document -H and -B

On 30-Jun-16 23:18, Brad King wrote: On 06/30/2016 03:56 PM, Ruslan Baratov wrote: What is the public-use way to specify source-tree and build-tree by cmake options simultaneously? cd $build && cmake $src Will not work if $build not exists. -- Powered by www.kitware.com Please keep

Re: [CMake] CMAKE_C_COMPILE_OBJECT vs

Hi, Can you explain what the goal of your compilation wrappers are? Are you trying to add a new compiler? On Wed, Jun 29, 2016 at 1:41 PM, Sam Cristall wrote: > Looks like this was just a change in CMake 3.4. Updated to latest, and > everything is working. >> On Jun

Re: [cmake-developers] [patch] Document -H and -B

On 06/30/2016 03:56 PM, Ruslan Baratov wrote: > What is the public-use way to specify source-tree and build-tree by > cmake options simultaneously? cd $build && cmake $src -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc4-641-gd2541c7

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

Re: [cmake-developers] [patch] Document -H and -B

On 30-Jun-16 22:31, Brad King wrote: On 06/30/2016 03:23 PM, Ruslan Baratov via cmake-developers wrote: Patch with undocumented options -H/-B. These are undocumented because they are internal options that are not meant for public use. What is the public-use way to specify source-tree and

Re: [cmake-developers] [patch] Document -H and -B

On 06/30/2016 03:23 PM, Ruslan Baratov via cmake-developers wrote: > Patch with undocumented options -H/-B. These are undocumented because they are internal options that are not meant for public use. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ

[cmake-developers] [patch] Document -H and -B

Hi, Patch with undocumented options -H/-B. Ruslo >From 6c378bd6622ca26c43225787494d60f1a9867b22 Mon Sep 17 00:00:00 2001 From: Ruslan Baratov Date: Thu, 30 Jun 2016 22:17:14 +0300 Subject: [PATCH] Document -H and -B options --- Help/manual/OPTIONS_BUILD.txt | 20

Re: [cmake-developers] cmake -E capabilities

On 06/30/2016 09:51 AM, Tobias Hunger wrote: > Compared to the bug report mentioned above the fields "multiconfig" and > "recursive" are missing. I could not figure out how to get that information:-/ There is no "recursive" generator, so that does not belong in the example anyway. The Makefile

Re: [CMake] How do you handle recursive dependencies in CMake

On 2016-06-30 10:59+0200 Sven Baars wrote: 2) ExternalProject which will grab a repository and build it. This will not work. One of the projects I use is Trilinos, which has build of around 1GB. I don't want to pull and build that for every project I have. Also the build flags that are used

Re: [cmake-developers] cmake -E capabilities

"Eclipse CDT4", > "KDevelop3", > "Kate", > "Sublime Text 2" > ], > "name" : "Unix Makefiles", > "toolSetSupport" : false > } >], >"

[CMake] CPack source package install location

Hi I have a very standard CPack configuration for deb package. I have two questions: 1. I generate the deb with: cpack --config CPackConfig.cmake -G "DEB" This is supposedly a binary package but when I install it on the machine I see header files being installed in /usr/include. Is this

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc4-639-g4969b98

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc4-289-g2bef377

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

[cmake-developers] cmake -E capabilities

"CodeLite", "Eclipse CDT4", "KDevelop3", "Kate", "Sublime Text 2"  ],  "name" : "Unix Makefiles",  "toolSetSupport" : false   }    ],    "server-

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc4-637-g4f12695

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc4-279-gb399d13

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc4-291-gb1883bc

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc4-287-g21afc02

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc4-277-g0639e23

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

Re: [CMake] How do you handle recursive dependencies in CMake

Hey again Marcel, Your reply got me thinking. I just checked again, and found that I just have to set the LIBRARY_PATH correctly as well. After that everything seems to work. Apparently this was not done in the right way. Since I have to use PATH anyway to find the FoobarConfig.cmake files, it is

Re: [CMake] CMake 3.6.0-rc4 now ready for testing!

On 06/29/2016 05:05 PM, Hendrik Sattler wrote: >> * The "InstallRequiredSystemLibraries" module learned a new >> "CMAKE_INSTALL_UCRT_LIBRARIES" option to enable app-local deployment >> of the Windows Universal CRT libraries with Visual Studio 2015. > > Maybe the help should note that this is

Re: [CMake] How do you handle recursive dependencies in CMake

Hey Marcel, They are indeed always set correctly, and for this reason, find_package is also always able to find these packages, which is great, and this is why I love using CMake, but then it still happens that when you don't explicitly use find_package, so in this case I don't use

Re: [CMake] How do you handle recursive dependencies in CMake

Hi Sven, Sorry to chime in so late. I was wondering, since you're mentioning large computer clusters, don't you use the "module" system to select which versions of which packages you want to use? If so, then (I assume) your PATH and LD_LIBRARY_PATH environment variables will have been set such

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc4-630-g0af6999

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

Re: [CMake] How do you handle recursive dependencies in CMake

I don't think this is a solution to the problem, since then it seems like the build will still fail for all our users unless they also build all their packages from inside hunter. If I wanted it to work just for myself I could just use hardcoded paths. The problem is that I want a portable way

Re: [CMake] How do you handle recursive dependencies in CMake

If find_project is not enough, and ExternalProject's only problem is build duplication, then I think it makes sense to consider a CMake-based dependency manager such as hunter: https://github.com/ruslo/hunter On Thu, Jun 30, 2016 at 3:59 AM, Sven Baars wrote: > This is a reply

[CMake] ctest: how to include pre- and post- processing commands

Hi, Apologize if I sent this twice. Is it possible to have a ctest which involves preprocessing as well as postprocessing. The code to test is myCode.exe, which writes an output file. PASS or FAIL is the result of comparison of output against reference data. Currently I use two add_tests:

Re: [CMake] How do you handle recursive dependencies in CMake

Hey Ray, For myself it is not a big problem either, but I don't want to tell users of my libraries that they have to look up how the administrators at their supercomputing facility compiled 20 other libraries so they can set their environment variables in the right way, while at the same time

Re: [CMake] How do you handle recursive dependencies in CMake

Hi Sven, On Thu, Jun 30, 2016 at 6:40 PM, Sven Baars wrote: > So let's take Trilinos as an example, which is quite a big library, > which depends on a lot of libraries as well. In every project that > builds upon it (but does not even use functionality of any libraries), > we

Re: [CMake] How do you handle recursive dependencies in CMake

Hi Ray, This still has the same problem. If I use FindBoost in project B, I can use BOOST_ROOT to be able to find it. This works fine. Now, if I try to compile project C, I can set B_ROOT for FindB, but then Boost will not be found, because it is not in B_ROOT, so project C will not compile. That

Re: [CMake] How do you handle recursive dependencies in CMake

Hi Sven, On Thu, Jun 30, 2016 at 4:59 PM, Sven Baars wrote: > This is a reply to the options that Ray gave. Here I will use the > package dependencies C -> B -> A{1,2}: Well, I presented some options to you. Perhaps there are others, but if none of them are right for you then

Re: [CMake] How do you handle recursive dependencies in CMake

This is a reply to the options that Ray gave. Here I will use the package dependencies C -> B -> A{1,2}: 1) The "ad-hoc" method I first mentioned by setting CMAKE_LIBRARY_OUTPUT_DIRECTORY. As far as I understand, this would mean that every user of all of the different projects would have to be

Re: [cmake-developers] adding FindJsonCpp

Hi, 2016-06-29 19:31 GMT+02:00 Ben Boeckel : > On Wed, Jun 29, 2016 at 17:36:45 +0200, Farbos a wrote: >> I have a concern with generating package configs: >> >> 1 It seems to contain absolute path, so not really portable with git. > > The actual config files are