[CMake] get complete list of compile definitions

Just in case anyone is interested - I found a hint in this old thread: https://cmake.org/pipermail/cmake/2014-February/056993.html Trick is to use a generator expression like this: "$" Regards, Robert Schwarzelt -- Powered by

Re: [CMake] cmake --graphviz not dumping custom target in the graph

I did not try that. It appears that none of my custom target do belong to ALL. I'll try right away and let you know. 2017-03-29 14:30 GMT+02:00 Craig Scott : > Does the behavior change if your custom target is part of the ALL target > or not? > > On Wed, Mar 29, 2017 at

[CMake] Fwd: cmake --graphviz not dumping custom target in the graph

-- Forwarded message -- From: Eric Noulard Date: 2017-03-29 17:50 GMT+02:00 Subject: Re: [CMake] cmake --graphviz not dumping custom target in the graph To: Craig Scott After checking this does not change. It seems that the only

[CMake] ZERO_CHECK generation and Xcode

If I understand correctly the purpose of the ZERO_CHECK target is to update the generated project files when necessary. That's fine, but I have noticed on Xcode (8.2) that when ZERO_CHECK runs and updates the project, it causes the xcode build to abort. Unfortunately, it seems this build abort

Re: [CMake] ZERO_CHECK generation and Xcode

Hi Steven, On 3/29/17 5:24 PM, Steven Velez wrote: > If I understand correctly the purpose of the ZERO_CHECK target is to update > the generated project files when necessary. > > That's fine, but I have noticed on Xcode (8.2) that when ZERO_CHECK runs > and updates the project, it causes the

[CMake] assembly on windows

Hi, Is there a simple way to get a Visual Studio + assembly project on windows? This seems to work on Linux: cmake_minimum_required(VERSION 3.7) project(assembler C ASM) set_source_files_properties(hello.s PROPERTIES COMPILE_FLAGS "-x assembler-with-cpp") add_executable(hello hello.s) What

Re: [CMake] ZERO_CHECK generation and Xcode

On 3/29/17 10:15 PM, Steven Velez wrote: > I do have a pretty large project with around 142 targets. > > Another characteristic of note, and which I noticed while investigating > this is that our project suffers from > https://gitlab.kitware.com/cmake/cmake/issues/14297, and I think it is >

[CMake] include() doesn't work with relative paths?

This fails: include( foo/bar/myscript.cmake ) But this works: include( ${CMAKE_CURRENT_LIST_DIR}/foo/bar/myscript.cmake ) Why are relative paths not working? -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware

Re: [CMake] Building third party libraries along with normal targets

On 30/03/2017 02:10, Robert Dailey wrote: Interested in hearing everyone's thoughts on this idea of mine. Right now I have several third party libraries: openssl, boost, libpng, zlib, etc. List goes on. I need to support these libraries on at least 3 different platforms: ARM android, x86 linux,

Re: [CMake] Building third party libraries along with normal targets

On Wed, Mar 29, 2017 at 8:18 PM, Florent Castelli wrote: > This is known as "super build". > Yes, this is exactly why I made my Boost CMake build scripts, which you use > unless you changed your mind today :) You mean this? https://github.com/Orphis/boost-cmake It's

Re: [CMake] Building third party libraries along with normal targets

On 30/03/2017 03:54, Robert Dailey wrote: On Wed, Mar 29, 2017 at 8:18 PM, Florent Castelli wrote: This is known as "super build". Yes, this is exactly why I made my Boost CMake build scripts, which you use unless you changed your mind today :) You mean this?

Re: [CMake] Building third party libraries along with normal targets

On Wed, Mar 29, 2017 at 9:32 PM, Florent Castelli wrote: > On 30/03/2017 03:54, Robert Dailey wrote: >> >> On Wed, Mar 29, 2017 at 8:18 PM, Florent Castelli >> wrote: >>> >>> This is known as "super build". >>> Yes, this is exactly why I

Re: [CMake] Building third party libraries along with normal targets

On 30/03/2017 04:38, Robert Dailey wrote: At the end of the day, I've solved the Boost problem but I have many other libraries I still manually build: openssl, libpng, zlib, etc. It's as you said, maintaining build scripts for all of these will be challenging but I think that's the proper way to

[CMake] Building third party libraries along with normal targets

Interested in hearing everyone's thoughts on this idea of mine. Right now I have several third party libraries: openssl, boost, libpng, zlib, etc. List goes on. I need to support these libraries on at least 3 different platforms: ARM android, x86 linux, x86 windows. It's a real pain in the rear

[CMake] gnu-arm-embedded toolchain and CMAKE_FORCE_C_COMPILER

Hi @all, In recent CMake versions I get a deprecated message for using the cmake_force_xxx_compiler() function inside my toolchain file. After searching, I found that there are two threads on the CMake list, one https://cmake.org/pipermail/cmake/2016-February/062773.html just ending without a

[CMake] get complete list of compile definitions

Hi all, I need to implement a code export function, that will only export code used in a specific project configuration. For this purpose I want to use unifdef (http://dotat.at/prog/unifdef/), which is capable of removing unused #ifdef blocks. The project uses static libraries like in following

[CMake] cmake --graphviz not dumping custom target in the graph

Hi all, It appears that cmake --graphviz command line option does not dump custom target in the generated dot graph but "only" target appearing in add_executable or add_library (plain or IMPORTED). Is there any fundamental reason for that ? I'd like to see ALL target (including custom) in my

Re: [CMake] cmake --graphviz not dumping custom target in the graph

Does the behavior change if your custom target is part of the ALL target or not? On Wed, Mar 29, 2017 at 10:37 PM, Eric Noulard wrote: > Hi all, > > It appears that cmake --graphviz command line option does not dump custom > target > in the generated dot graph but

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-626-gc9728d7

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-620-g4f7e913

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 discards 70de6381a92d919c050e2067c54a0943db2c493f (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-613-g6a5a214

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

[Cmake-commits] CMake branch, release, updated. v3.8.0-rc3-18-gd4a9957

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, release has been updated via d4a995750a1e3101f943a0d2e91fc9688f5e23f7 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-618-g70de638

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 discards f0932bf2b802983f5c6b72c03fbd321bfeb0b6a6 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-611-g6dc7262

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-634-gaf34df7

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-636-g0e71929

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-623-gbdc5141

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

[cmake-developers] Email addresses of Mantis bug reporters

Hello, while walking through old bug reports contacting the reporters by email would be helpful sometimes. Is there a way for me access this information in Mantis? Thanks, Gregor -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [cmake-developers] Email addresses of Mantis bug reporters

On 03/29/2017 03:59 PM, Gregor Jasny via cmake-developers wrote: > while walking through old bug reports contacting the reporters by email > would be helpful sometimes. Is there a way for me access this > information in Mantis? I don't think that information is publicly accessible in Mantis.

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-638-gfcb2d3e

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-613-gf0932bf

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 discards 6543b1b9b1109f14292a3a63546f44ab22e0ed48 (commit) discards

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc3-638-gfcb2d3e

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, nightly has been updated discards 896e195588bde813ad6e0cc8af7fe1594d37907c (commit) discards

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc3-613-g6a5a214

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, nightly-master has been updated via 6a5a214f4383fbe3dd6de4747aba43088701 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-639-g8484d6e

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 discards fcb2d3e17b5cfc3c0a98dad59a56e0022ba92541 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc3-614-gf6d802b

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 f6d802b5bcd201f48c7af47f27ec9e1dd0062171 (commit) from

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc3-615-g6543b1b

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