Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Nils Gladitz
On 11/09/2016 09:06 PM, Ruslan Baratov wrote: So why the project in the middle of the migration process is not a valid case? It is maintained but the exact migration step is paused, but I have an intention to improve the code in future. Anyway even if the project is no longer maintained, then w

Re: [CMake] Is there a default value for CMAKE_MODULE_PATH?

2016-11-09 Thread Jayesh Badwaik
All of these version work, but because of the various kinds of automated setups I use, the command line options seems the best compromise. However, I realized that I have a include file in my source code which is ignored from the source control since it is user/system dependent, and I have put

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Ruslan Baratov via CMake
On 09-Nov-16 23:00, Nils Gladitz wrote: > On 09.11.2016 15:52, Ruslan Baratov wrote: >> Can you show the real code? The code that in your opinion doesn't >> violate the "right way of policy usage"? > > It is not a question about code. It is a question about context and > use case. You just said tha

Re: [CMake] Is there a default value for CMAKE_MODULE_PATH?

2016-11-09 Thread Wagner, David
On 09/11/2016 16:05, Jayesh Badwaik wrote: Hi, TL;DR Is there a default value for CMAKE_MODULE_PATH which allows me to use a module file from inside my PROJECT_SOURCE_DIR. Context: Over past few days, Boost has updated from version 1.61 to version 1.62. The latest version of CMake that I have (

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Nils Gladitz
On 09.11.2016 15:52, Ruslan Baratov wrote: Can you show the real code? The code that in your opinion doesn't violate the "right way of policy usage"? It is not a question about code. It is a question about context and use case. Valid context as the documentation states would e.g. be a projec

Re: [CMake] PDB_NAME with DEBUG_POSTFIX

2016-11-09 Thread Carl Poirier
Hi folks, A few months later, would anyone have an explanation for this? Thank you, Carl On Fri, Feb 19, 2016 at 9:07 AM, Carl Poirier wrote: > Hi folks, > > I have a question here regarding the use of the DEBUG_POSTFIX. When I set > it as well as the property OUTPUT_NAME, the former is corre

[CMake] Is there a default value for CMAKE_MODULE_PATH?

2016-11-09 Thread Jayesh Badwaik
Hi, TL;DR Is there a default value for CMAKE_MODULE_PATH which allows me to use a module file from inside my PROJECT_SOURCE_DIR. Context: Over past few days, Boost has updated from version 1.61 to version 1.62. The latest version of CMake that I have (3.6.3) does not yet have the appropriate F

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Ruslan Baratov via CMake
Can you show the real code? The code that in your opinion doesn't violate the "right way of policy usage"? On 09-Nov-16 22:14, Nils Gladitz wrote: > On 09.11.2016 14:57, Ruslan Baratov wrote: >> >> Again policies are not meant to be feature toggles. >> You can do a lot of things and there may be v

Re: [CMake] Pointing CMAKE_AUTOMOC to a custom version of Qt and its moc.exe

2016-11-09 Thread Saad Khattak
Hmm, maybe...? I'm not sure. Customize may be the wrong word. What I'm asking in the question is similar to someone asking "how do I customize the output path for the binaries in CMake?". My hope was it was going to be a simple set variable for the utilities. On Wed, Nov 9, 2016, 7:56 AM Jakob van

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Nils Gladitz
On 09.11.2016 14:57, Ruslan Baratov wrote: Again policies are not meant to be feature toggles. You can do a lot of things and there may be valid use cases but in general policies are not meant to be used this way. This is made explicit in CMake's documentation on policies. They exist to preser

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Ruslan Baratov via CMake
On 09-Nov-16 19:51, Nils Gladitz wrote: > On 09.11.2016 12:04, Ruslan Baratov wrote: >> On 09-Nov-16 16:22, Nils Gladitz wrote: >>> On 09.11.2016 04:29, Ruslan Baratov wrote: On 08-Nov-16 23:33, Nils Gladitz wrote: > On 11/08/2016 04:17 PM, Ruslan Baratov wrote: > >> Except it's ex

Re: [CMake] Pointing CMAKE_AUTOMOC to a custom version of Qt and its moc.exe

2016-11-09 Thread Jakob van Bethlehem
Hej, On Mon, Nov 7, 2016 at 4:48 PM, Saad Khattak wrote: > I am working on a plugin for Maya and it uses a customized version of Qt. > Maya's SDK comes with everything to build Qt (headers, libraries and > customized Qt tools such as moc.exe). > > I have the following issues: > > (1) With CMAKE_

Re: [CMake] Get libraries from target

2016-11-09 Thread Jakob van Bethlehem
Hej, You should be able to query the LINK_LIBRARIES (and maybe some related properties), see https://cmake.org/cmake/help/v3.6/prop_tgt/LINK_LIBRARIES.html Sincerely, Jakob On Wed, Nov 9, 2016 at 12:05 AM, Tiago Macarios wrote: > Hi, > > Is there a way for me to get CMake libraries out of a t

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Jakob van Bethlehem
Oops, totally forgot to mention the crux: I happened to be the guy who apparently was the first to start using continue() - so by the time my college got to me, we quickly found out the issue. But before the college hit the problem, I didn't have the vaguest clue that I was typing code that would r

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Jakob van Bethlehem
+1 for me too - sometime ago a college of mine spend quite some time to figure why he couldn't bootstrap our application - turns out he was using an (old) CMake version which didn't know about the 'continue' command. The error-messages coming out of CMake sometimes help, but more often don't really

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Nils Gladitz
On 09.11.2016 12:04, Ruslan Baratov wrote: On 09-Nov-16 16:22, Nils Gladitz wrote: On 09.11.2016 04:29, Ruslan Baratov wrote: On 08-Nov-16 23:33, Nils Gladitz wrote: On 11/08/2016 04:17 PM, Ruslan Baratov wrote: Except it's exactly opposite :) `cmake_minimum_required` is about new features/c

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Ruslan Baratov via CMake
On 09-Nov-16 16:22, Nils Gladitz wrote: > On 09.11.2016 03:47, Ruslan Baratov wrote: >> On 09-Nov-16 06:01, Nils Gladitz wrote: >>> I think the git tag creation dates should roughly equate release dates: >>> https://cmake.org/gitweb?p=cmake.git;a=tags >> What about the future releases? There w

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Ruslan Baratov via CMake
On 09-Nov-16 16:22, Nils Gladitz wrote: > On 09.11.2016 04:29, Ruslan Baratov wrote: >> On 08-Nov-16 23:33, Nils Gladitz wrote: >>> On 11/08/2016 04:17 PM, Ruslan Baratov wrote: >>> Except it's exactly opposite :) `cmake_minimum_required` is about new features/commands, and policies is ab

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Nils Gladitz
On 09.11.2016 03:47, Ruslan Baratov wrote: On 09-Nov-16 06:01, Nils Gladitz wrote: I think the git tag creation dates should roughly equate release dates: https://cmake.org/gitweb?p=cmake.git;a=tags What about the future releases? There was a page https://cmake.org/Bug/changelog_page.php b

Re: [CMake] Adding Cmake version in online documentation

2016-11-09 Thread Nils Gladitz
On 09.11.2016 04:29, Ruslan Baratov wrote: On 08-Nov-16 23:33, Nils Gladitz wrote: On 11/08/2016 04:17 PM, Ruslan Baratov wrote: Except it's exactly opposite :) `cmake_minimum_required` is about new features/commands, and policies is about behavior. I don't agree and you can not separate the