[Cmake-commits] CMake branch, master, updated. v3.11.0-rc4-277-g9fae23f

VERSION_MINOR 11) -set(CMake_VERSION_PATCH 20180320) +set(CMake_VERSION_PATCH 20180321) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[CMake] target_compile_features no known features for CXX compiler for clang 9.0

Trying to build Ceres, I'm running into an issue in which CMake 3.11.0-rc3 doesn't seem to recognize the clang that comes with the latest Xcode (Version 9.2 (9C40b)). Googling turns up similar, but old results, that seem to suggest one needs to update CMake. But -rc4 is the only more recent

Re: [CMake] CTest extra tests

> On Mar 20, 2018, at 9:45 AM, Bill Hoffman wrote: > > Must be coming from some macro, cmake does not automatically add any tests. > You could run cmake --trace and look at the output and find out where the > add_test call is coming from. Thanks, that was it! The

Re: [CMake] [proposal] Support for modern CMake

On 20 March 2018 at 21:52, Alexander Neundorf wrote: > On 2018 M03 20, Tue 21:14:30 CET Mateusz Loskot wrote: > ... >> Why I can not write: >> >> target_use(app Boost::system Boost::filesystem) >> >> or >> >> target_use_targets(app Boost::system Boost::filesystem) >> >> and,

Re: [CMake] [proposal] Support for modern CMake

On 2018 M03 20, Tue 21:14:30 CET Mateusz Loskot wrote: ... > Why I can not write: > > target_use(app Boost::system Boost::filesystem) > > or > > target_use_targets(app Boost::system Boost::filesystem) > > and, actually read and understand what I'm doing? > > (If you're now typing "why don't

[CMake] [proposal] Support for modern CMake

Hi, I've used CMake for a 10+ years now. I'm not a newbie, but I still discover CMake awesomeness as well as its traps. Now, I'm trying to catch up with the modern CMake party and I obviously watched the famous Daniel Pfeifer's lecture [1] (I'm late, I know!) I asked a simple question on #cmake

Re: [CMake] CTest extra tests

Must be coming from some macro, cmake does not automatically add any tests. You could run cmake --trace and look at the output and find out where the add_test call is coming from. On Sun, Mar 18, 2018 at 5:39 PM, Adam Getchell wrote: > Hello all, > > I’m running into

[CMake] file(TO_NATIVE_PATH ... ) and cross-compiling

Hi! I have question concerning the file(TO_NATIVE_PATH ...) behavior. The documentation says: "The TO_NATIVE_PATH mode converts a cmake-style into a native path with platform-specific slashes (\ on Windows and / elsewhere)." ... but it doesn't say if the decision is made based on the

[Cmake-commits] CMake branch, master, updated. v3.11.0-rc4-276-g1c3bbda

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

[Cmake-commits] CMake branch, master, updated. v3.11.0-rc4-272-g3b99c96

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

Re: [cmake-developers] How to get cmake to install pdb files for targets too?

Hi, On 20.03.2018 08:05, Claus Klein wrote: > Hi, I am wondering why pdb file are not installed with a library target > in MS VS2017 generated projects when building the Debug config variant? Very few people install PDBs to the bin directory, that is an administrative nightmare (who is

[cmake-developers] How to get cmake to install pdb files for targets too?

Hi, I am wondering why pdb file are not installed with a library target in MS VS2017 generated projects when building the Debug config variant? Is this relay necessary: install(FILES $ DESTINATION bin OPTIONAL) see too