[Cmake-commits] CMake branch, master, updated. v3.6.0-rc3-236-g3a04494

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

Re: [CMake] CMake terminology

There is cmake **build** step: cmake --build _builds So in GUI it's: * cmake configure * cmake generate * IDE build (which you can do with cmake --build so it can be called "cmake build" step) in cmd: * cmake configure+generate * cmake build Also I can call it "cmake step" in docs about

Re: [CMake] CMake terminology

In documentation, blog articles, etc. I just call it the "cmake" step (or sometimes the "project setup" step if talking in a more project-wide sense). For many users, the separate configure and generate steps are somewhat of an implementation detail, so it makes more sense to give it a single

Re: [CMake] CMake terminology

On 24-Jun-16 23:49, Robert Maynard wrote: Please run the configure and generate steps by It's too long :) Also it doesn't express the fact that it's a single action, consider: "To add variables on configure and generate steps use '-D'" "Before running configure and generate steps note that

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-530-g2152e11

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

[CMake] Qt 5.6.1 messes up Linux packaging using CPack?

I have a project that uses CMake. I had been compiling against Qt 5.6.0 for a while but due to issues with QWebEngine I installed Qt 5.6.1 instead and compiled against that. I can run my application from the build directory but when I go to use cpack to package my application I am getting the

Re: [CMake] CMake terminology

Please run the configure and generate steps by On Fri, Jun 24, 2016 at 4:40 PM, Ruslan Baratov wrote: > > On 24-Jun-16 23:25, Robert Maynard wrote: >> >> cmake from the command line is still running the two stages, it just >> doesn't allow for feedback/input from the

Re: [CMake] CMake terminology

On 24-Jun-16 23:25, Robert Maynard wrote: cmake from the command line is still running the two stages, it just doesn't allow for feedback/input from the user between the two stages. Yes, I understand that. Question is about the name of the step. I.e. when I do write manual what should I choose

Re: [CMake] CMake terminology

cmake from the command line is still running the two stages, it just doesn't allow for feedback/input from the user between the two stages. On Fri, Jun 24, 2016 at 4:06 PM, Ruslan Baratov via CMake wrote: > Hi, > > I have a question about CMake terminology. When we are using

[CMake] CMake terminology

Hi, I have a question about CMake terminology. When we are using CMake GUI there are two buttons "Configure" and "Generate", hence we have two stages: 1. Configure step, when we do configuring project, effectively creating file with cache variables (which we can modify) without really

[cmake-developers] Improved handling of %directives in CPACK_RPM_USER_FILELIST

Attached is a patch to improve the handling of %directives in CPACK_RPM_USER_FILELIST. Specifically it accepts any characters (even spaces) inside the parenthesis so it doesn't need to keep changing every time there's a new valid symbol. The current open ticket is

Re: [CMake] gathering directory names in cmake

> I have a source tree which contains multiple directories each of > which has a subdirectory called "xyz". I want to create a target > that creates a zip file with each of the xyz directories. You can filter the file paths with a few CMake script lines: file(GLOB_RECURSE FILES "./*")

[CMake] subversion

Dear cmake users, I have a question if, and how, you use the Subversion module of cmake. The module provides the macro Subversion_WC_INFO, which extracts information of a working copy. I use this information, to generate a sub minor revision number of my project. If I checkout my project using

[cmake-developers] Status of pre-compiled headers

Hello! As far as I can see from issue tracker and the mail list archives of "precompiled headers" feature we are still struggling for solution. I'm ready to contribute to development, but have not idea where shall I start :) https://cmake.org/Bug/view.php?id=1260

[cmake-developers] [ANNOUNCE] DaD's House Standalone Installers

Hello dear developers! Standalone installers for some DaD's House releases now available at SF mirror: https://sourceforge.net/projects/dad-mirror/files/standalone/2015/dad-0.3.1-windows-vc12x64-2015-standalone.exe/download

Re: [cmake-developers] daemon-mode meeting last Tuesday

On Fri, Jun 24, 2016 at 5:24 PM, Tobias Hunger wrote: > Hi Daniel, > > On Fri, Jun 24, 2016 at 5:08 PM, Daniel Pfeifer > wrote: Currently cmake-gui supports switching generators, build trees, etc., so there is some precedent for such

Re: [cmake-developers] daemon-mode meeting last Tuesday

Hi Daniel, On Fri, Jun 24, 2016 at 5:08 PM, Daniel Pfeifer wrote: >>> Currently cmake-gui supports switching generators, build trees, etc., so >>> there is some precedent for such switching within a single process. If >>> we have (re-)initialization bugs they should

[CMake] Configuring CxxTest

Hello, I setup my first cmake projet, but I have some problems with generating my CxxTest suite. I can easily call up the CxxTest packgage and specify the generator using "CXXTEST_PYTHON_TESTGEN_EXECUTABLE" following the instruction of the documentation

Re: [cmake-developers] daemon-mode meeting last Tuesday

On Fri, Jun 24, 2016 at 4:56 PM, Tobias Hunger wrote: > Hi Brad, > > On Thu, Jun 23, 2016 at 10:46 PM, Brad King wrote: >>> * This is currently used to set sourcedirectory, builddirectory and >>> generator. >>> >>> These three should be

Re: [cmake-developers] daemon-mode meeting last Tuesday

Hi Brad, On Thu, Jun 23, 2016 at 10:46 PM, Brad King wrote: >> * This is currently used to set sourcedirectory, builddirectory and >> generator. >> >> These three should be passed in via the command line instead, again >> to avoid trouble with users switching

Re: [cmake-developers] daemon-mode meeting last Tuesday

Hallo Daniel, On Fri, Jun 24, 2016 at 9:59 AM, Daniel Pfeifer wrote: > On Thu, Jun 23, 2016 at 2:27 PM, Tobias Hunger wrote: >> * We both think it only makes sense to merge the infrastructure part into >> cmake (if it passes review first of

Re: [cmake-developers] daemon-mode meeting last Tuesday

On Thu, Jun 23, 2016 at 2:27 PM, Tobias Hunger wrote: > * We both think it only makes sense to merge the infrastructure part into > cmake (if it passes review first of course) once we have some > functionality > that is genuinely useful. So we want to aim at having

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-525-g41a5113

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