[Cmake-commits] CMake branch, master, updated. v3.7.0-rc3-445-g25085f4

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

Re: [CMake] Adding Cmake version in online documentation

On 08-Nov-16 23:33, Nils Gladitz wrote: > On 11/08/2016 04:17 PM, Ruslan Baratov wrote: > >> On 08-Nov-16 22:22, Nils Gladitz wrote: >>> Strictly speaking cmake_minimum_required(VERSION) is not about command >>> availability but rather about behavior (cmake policies). >> Except it's exactly

Re: [CMake] Adding Cmake version in online documentation

On 09-Nov-16 06:01, Nils Gladitz wrote: > On 08.11.2016 20:26, Albrecht Schlosser wrote: > >> >> I'd like to have a list of release dates (I'm not sure if there is >> one) as well as the exact version a feature was introduced to write >> CMakeLists.txt files that run on really old CMake versions.

Re: [CMake] Adding Cmake version in online documentation

On 08.11.2016 23:01 Nils Gladitz wrote: On 08.11.2016 20:26, Albrecht Schlosser wrote: I'm a developer of a public GUI library (FLTK). In this position you don't know anything about the availability of CMake versions on your target platforms. Our intention is to keep cmake_minimum_required()

Re: [CMake] Adding Cmake version in online documentation

On 08.11.2016 22:23 Eric Noulard wrote: 2016-11-08 20:26 GMT+01:00 Albrecht Schlosser <...>: I'd also like such an addition to the documentation for reasons discussed below. I think the need is recognized by most CMake user but... okay... Strictly speaking

[CMake] Get libraries from target

Hi, Is there a way for me to get CMake libraries out of a target? For example: target_link_libraries(A B C) Can I get B and C from A? What I am trying to do: We are working on adding include-what-you-use into our build system and some of the libraries have their on mapping files. So I was

Re: [CMake] Adding Cmake version in online documentation

On 08.11.2016 20:26, Albrecht Schlosser wrote: On 08.11.2016 15:22 Nils Gladitz wrote: Strictly speaking cmake_minimum_required(VERSION) is not about command availability but rather about behavior (cmake policies). [...] I'd start by requesting the highest possible version I could justify

Re: [CMake] Adding Cmake version in online documentation

Rather than trying to do everything, perhaps there's value in tackling this in stages. At a high level, simply knowing in which CMake version a particular command, property, variable or module was added is a good start. >From there, if a command, etc. gained new options, then a note could be added

Re: [CMake] Adding Cmake version in online documentation

2016-11-08 20:26 GMT+01:00 Albrecht Schlosser : > On 08.11.2016 15:22 Nils Gladitz wrote: > >> On 11/08/2016 03:11 PM, Dvir Yitzchaki wrote: >> >> But how do you know which version to declare on cmake_minimum_required? >>> If this feature will be added it won't be far

Re: [CMake] Adding Cmake version in online documentation

On 08.11.2016 15:22 Nils Gladitz wrote: On 11/08/2016 03:11 PM, Dvir Yitzchaki wrote: But how do you know which version to declare on cmake_minimum_required? If this feature will be added it won't be far from writing a script that scans the commands you use and outputs the first appropriate

Re: [cmake-developers] cmake 3.7.0-rc3 regression

On 11/08/2016 02:16 PM, Robert Goulet wrote: > + if (cmSystemToolsCMakeRoot.empty()) { > +std::string dir = cmSystemTools::GetFilenamePath(exe_dir); Please see my sibling response for why more logic is needed. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check

Re: [cmake-developers] cmake 3.7.0-rc3 regression

Anyhow, here's a quick patch that fixes it. Thanks. -Original Message- From: Robert Goulet Sent: Tuesday, November 8, 2016 2:09 PM To: 'Rolf Eike Beer' ; cmake-developers@cmake.org Subject: RE: [cmake-developers] cmake 3.7.0-rc3 regression Not sure I understand why is

Re: [cmake-developers] cmake 3.7.0-rc3 regression

On 11/08/2016 01:59 PM, Robert Goulet wrote: > Commit: 18bfbc972fd3daf3e973f80072c4de09ec7e852b > Add option to control 'bin' directory of CMake's own installation (#16076) I suspect it is caused by this hunk: > - // Install tree has "/bin/cmake" and "". > - std::string dir =

Re: [cmake-developers] cmake 3.7.0-rc3 regression

Am Dienstag, 8. November 2016, 18:59:34 schrieb Robert Goulet: > Hi, > > After trying to upgrade to CMake 3.7.0-rc3, we've found the following > regression: > > Previously, we were able to put multiple platform CMake executables in the > same root by just renaming the "bin" folder, so that they

Re: [cmake-developers] cmake 3.7.0-rc3 regression

Not sure I understand why is this part of a build switch now? And what if we don't build CMake ourselves but instead, using prebuilt binaries from the CMake website? -Original Message- From: Rolf Eike Beer [mailto:e...@sf-mail.de] Sent: Tuesday, November 8, 2016 2:04 PM To:

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-983-g9b7016e

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

Re: [CMake] Force MSVC runtime for debug builds

I would agree. I don't know how many subtle runtime bugs I have had to figure out because our project mixed debug and release runtimes on MSVC. DON'T do it unless you REALLY have to. But even then I would never actually deploy that into production. YMMV -- Mike Jackson

[cmake-developers] cmake 3.7.0-rc3 regression

Hi, After trying to upgrade to CMake 3.7.0-rc3, we've found the following regression: Previously, we were able to put multiple platform CMake executables in the same root by just renaming the "bin" folder, so that they don't overlap each other, as such: cmake/win/cmake.exe cmake/mac/cmake

Re: [CMake] additional arguments with CMAKE_CXX_CLANG_TIDY variable

> On Nov 8, 2016, at 10:06 AM, Bill Hoffman wrote: > > On 11/8/2016 11:20 AM, Michael Ellery wrote: >> /usr/local/Cellar/cmake/3.6.2/bin/cmake -E __run_iwyu >> --tidy="/usr/local/opt/llvm38/bin/clang-tidy-3.8;-checks=*" >> --source=/Users/ellery/work/. > That

Re: [CMake] additional arguments with CMAKE_CXX_CLANG_TIDY variable

On 11/8/2016 11:20 AM, Michael Ellery wrote: /usr/local/Cellar/cmake/3.6.2/bin/cmake -E __run_iwyu --tidy="/usr/local/opt/llvm38/bin/clang-tidy-3.8;-checks=*" --source=/Users/ellery/work/. That should still work. It is passing that to -E __run_iwyu which should expand the arguments.

Re: [CMake] Force MSVC runtime for debug builds

- On Nov 7, 2016, at 1:37 AM, Stephan Menzel wrote: > Hello everyone, > I'm looking for a way to force Debug configurations in generated MSVC > solutions > to use the Release runtime instead of the default "Debug". e.g. /MD rather > than > /MDd. > My use case

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-981-g3cc9809

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-979-g0f1eae2

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-977-g4e34731

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

[CMake] additional arguments with CMAKE_CXX_CLANG_TIDY variable

I asked this question on SO and am repeating here with the hope someone knows the answer: http://stackoverflow.com/questions/40433573/how-can-i-specify-additional-arguments-for-use-with-cmake-cxx-clang-tidy-variabl —— I'm trying to use make use of clang-tidy integration with cmake and I'd like

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-971-g3f7b09c

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

Re: [CMake] Adding Cmake version in online documentation

On 11/08/2016 04:17 PM, Ruslan Baratov wrote: On 08-Nov-16 22:22, Nils Gladitz wrote: Strictly speaking cmake_minimum_required(VERSION) is not about command availability but rather about behavior (cmake policies). Except it's exactly opposite :) `cmake_minimum_required` is about new

Re: [CMake] CMake 3.7.0-r2 Open Project sometimes picks wrong version of Visual Studio

- On Nov 8, 2016, at 8:13 AM, Taylor Braun-Jones tay...@braun-jones.org wrote: > On Fri, Nov 4, 2016 at 2:55 PM, Brad King wrote: >> >> On 11/03/2016 06:04 PM, John Drescher wrote: >> > I opened a project in cmake-gui using the open project button from a >> > vc

Re: [CMake] Adding Cmake version in online documentation

On 08-Nov-16 22:11, Dvir Yitzchaki wrote: > But how do you know which version to declare on cmake_minimum_required? I do hit this too. This would be a very useful feature. Sometimes I have to manually "scan" the docs to figure out some simple facts about newly introduces variables/commands. On

Re: [CMake] CMake 3.7.0-r2 Open Project sometimes picks wrong version of Visual Studio

On Fri, Nov 4, 2016 at 2:55 PM, Brad King wrote: > > On 11/03/2016 06:04 PM, John Drescher wrote: > > I opened a project in cmake-gui using the open project button from a > > vc 2010 build of a project. The open project opened the project in > > Visual Studio 2010. Later I

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-966-g38ec4b1

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-964-gedca8b6

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-950-g36bf6fd

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-962-gb40c0bb

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-960-ga5b31cd

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc3-444-g666bb0e

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc3-442-g4ec359b

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc3-431-g69bb9f3

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-rc3-436-g049b10e

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc3-952-gddb04eb

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

Re: [CMake] Adding Cmake version in online documentation

On 11/08/2016 03:11 PM, Dvir Yitzchaki wrote: But how do you know which version to declare on cmake_minimum_required? If this feature will be added it won't be far from writing a script that scans the commands you use and outputs the first appropriate version. Strictly speaking

Re: [CMake] Adding Cmake version in online documentation

But how do you know which version to declare on cmake_minimum_required? If this feature will be added it won't be far from writing a script that scans the commands you use and outputs the first appropriate version. Regards, Dvir -Original Message- From: CMake

Re: [CMake] Adding Cmake version in online documentation

On 11/08/2016 10:57 AM, Louis-Paul CORDIER wrote: Hi, This is a feature proposal for the documentation. Cmake is making use of cmake_minimum_required() command, that is very useful. Unfortunately it is very hard to identify commands that will work without browsing all version of cmake

Re: [CMake] Adding Cmake version in online documentation

+1 -- Mike Jackson [mike.jack...@bluequartz.net] Louis-Paul CORDIER wrote: Hi, This is a feature proposal for the documentation. Cmake is making use of cmake_minimum_required() command, that is very useful. Unfortunately it is very hard to identify commands that will work without browsing

[CMake] Adding Cmake version in online documentation

Hi, This is a feature proposal for the documentation. Cmake is making use of cmake_minimum_required() command, that is very useful. Unfortunately it is very hard to identify commands that will work without browsing all version of cmake documentation for a given command. That said, adding a