[Cmake-commits] CMake branch, master, updated. v3.5.2-798-gadc7fcd

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

Re: [CMake] How to hundle gcc link options(like whole-archive, --allow-multiple-definition) in CMake？

Thanks for your generous Mr. Atkins, what you answer me worked well and solved my question. I would keep 'always use target names in a CMakeLists.txt instead of the actual output file' in my mind. :-) Chao Chuck Atkins wrote > Hi Chao, > > You want to let CMake to as much of the work for you as

[cmake-developers] [CMake 0016133]: NO_DEFAULT_PATH is taken as a path when specified after the PATHS option.

The following issue has been SUBMITTED. == https://public.kitware.com/Bug/view.php?id=16133 == Reported By:Alexis Wilke Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.5.2-1627-g2fdaa20

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1625-ge4bfebd

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1623-gd85aa58

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1621-gd975bf0

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1619-gb133045

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

[cmake-developers] Topic "add-opencl-imported-target" good to merge?

Hi, I've just pushed "add-opencl-imported-target" which adds an imported target to FindOpenCL. The whole change is rather small: https://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=6c53137a19e482140db3dc97b626af38348f2c71 Good to merge this to next for testing? Cheers, Matthäus --

Re: [cmake-developers] output expressions fails with either a build.ninja error or wrong escaped space

On 05/31/2016 02:28 PM, jerry@web.de wrote: > thanks for the response. I was eager to solve this. I came up > with this solution: > > -I$,\t-I> > > I searched for a solution where i can use it without the quotes > while the tab (\t) takes

Re: [cmake-developers] output expressions fails with either a build.ninja error or wrong escaped space

Hi, thanks for the response. I was eager to solve this. I came up with this solution: -I$,\t-I> I searched for a solution where i can use it without the quotes while the tab (\t) takes care that it is recognized as a generator expression.

Re: [cmake-developers] output expressions fails with either a build.ninja error or wrong escaped space

Hi,   thanks for the response. I was eager to solve this. I came up with this solution:   -I$,\t-I>   I searched for a solution where i can use it without the quotes while the tab (\t) takes care that it is recognized as a generator

Re: [cmake-developers] [MODERN] CMake ~3.6 vs Qt 5.6 vs MSVC2015

Hi all! Modern master updated! :-) It's time to upgrade: CMake 3.5.20160531 now available! Previously had problems with that, but now it seems that it works. Let me remind you of the link. Windows 32bit: http://ifw.podsvirov.pro/cmake/cmake-master-win32-online.exe Windows 64bit:

Re: [CMake] CMake+QT always failed for the first build, and succeeded for second build or later.

It seems CMakw could not find the generated moc_xxx files. I modified the scripts to specify moc_xxx files is generated, but it still has same errors. ADD_CUSTOM_COMMAND ( OUTPUT ${Qt_tmp}/moc_GMWindow.cpp COMMAND ${QT_MOC_CMD} ${GM_DIR}/GMWindow.h -o

Re: [CMake] C header file cross dependency

Thank you for your answer! > > How do I resolve something like this? Right now CMake evaluates the > > compiler includes in the order that subdirectories are added. This > > gives me an compilation error in uart.c that terminal.h cannot be > > found. > > This is not a cmake-problem, but seems to

[Cmake-commits] CMake branch, next, updated. v3.5.2-1615-g875eb5d

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

[Cmake-commits] CMake branch, next, updated. v3.5.2-1617-gdb87c9d

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

[Cmake-commits] CMake branch, master, updated. v3.5.2-797-gebcc13e

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

Re: [cmake-developers] output expressions fails with either a build.ninja error or wrong escaped space

On 05/28/2016 01:15 PM, jerry@web.de wrote: > "-I$, -I>" This tells CMake to generate a single argument consisting of the entire expanded value. We have no syntax to expand lists into multiple command line arguments after evaluation of

Re: [CMake] How to hundle gcc link options(like whole-archive, --allow-multiple-definition) in CMake？

Hi Chao, You want to let CMake to as much of the work for you as possible. You're still trying to explicitly pass the path to the library file to target_link_libraries. If you look at the line: target_link_library(exe1 "-Wl, --whole-archive ../sub_dir1/liblib1.a --no-whole-archive") there's