[Cmake-commits] CMake branch, master, updated. v3.6.1-734-gff88df4

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1471-g81bb94a

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

[cmake-developers] [PATCH] QtCreator integration: C++ includes must come first

Hello, When using the Clang Code Model in QtCreator, it turned out that having the C system include dirs can make it report false positives for most uses on the STL. This is due to the order the Clang Code Model looks at the include directories and some C includes in /usr/include could be

Re: [CMake] Time each target

> On Aug 25, 2016, at 9:58 AM, Moreland, Kenneth wrote: > > Does anyone know of a simple way to get CMake to time how long it takes to > compile each target? As it stands now, when compiling a CMake-managed project > a status is printed before each target is built. What I

[Cmake-commits] CMake branch, next, updated. v3.6.1-1453-g5a38fe2

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

Re: [CMake] Only install one component in cpack

Thx. Works perfectly :-D Am 25.08.2016 13:56 schrieb "Eric Noulard" : > Hi Tonka, > > You should read the doc here: > https://cmake.org/cmake/help/v3.5/module/CPackComponent.html > > for the ZIP generator you should > > set(CPACK_ARCHIVE_COMPONENT_INSTALL ON) > this is

[CMake] Time each target

Does anyone know of a simple way to get CMake to time how long it takes to compile each target? As it stands now, when compiling a CMake-managed project a status is printed before each target is built. What I am looking for is a way to get CMake to print a second status message after the target

[CMake] Erroneous CMP0022 warning for transitive conditional link dependencies?

Hi all, As it seems you get an erroneous CMP0022 warning in the following scenario, due to a generator expression not being resolved before string comparison. Confirmed with versions 3.5.1 and rev 00a583ac6833 . (2016-08-24 06:01:04) on Ubuntu Xenial using the Unix Makefile generator. - Create

[Cmake-commits] CMake branch, next, updated. v3.6.1-1450-gf80a411

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

Re: [cmake-developers] [PATCH] Make test driver clang-tidy clear

On 08/25/2016 06:04 AM, Sylvain Joubert wrote: > Please find attach a patch that clean the test driver source regarding > clang-tidy checks. Thanks, applied: create_test_sourcelist: Use safer strncpy instead of strcpy https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=cd344e3a -Brad --

[Cmake-commits] CMake branch, next, updated. v3.6.1-1447-gd89838e

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1445-g7ea8c85

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1443-gcd4b2e9

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1441-gd708b54

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

Re: [cmake-developers] [CMake] Setup/tear down steps for CTest

On Tue, Aug 23, 2016 at 08:00:09 +0200, Rolf Eike Beer wrote: > Am Dienstag, 23. August 2016, 10:06:01 schrieb Craig Scott: > > So how would you want the feature to work? I'd suggest an initial set of > > requirements something like the following: > > > >- Need to support the ability to

[Cmake-commits] CMake branch, next, updated. v3.6.1-1439-g826dd1e

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1436-g61a017f

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-731-ga79abb8

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-733-g98caa14

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-724-gce8fadc

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-722-gd1ee1cb

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

[Cmake-commits] CMake branch, master, updated. v3.6.1-720-gd8b70f6

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1429-ga668268

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1423-ge1f3f61

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

[Cmake-commits] CMake branch, next, updated. v3.6.1-1421-gbf1c52e

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

Re: [cmake-developers] VS Toolchain Support

On 08/24/2016 03:39 PM, Olmstead, Don wrote: > For a first pass it might be best to just follow what is in cmIDEFlagTable > as this would largely be unintrusive and just get the architecture there. Yes, let's go with a direct mapping for now. These files don't necessarily have to be pretty. On

[CMake] CUDA: COMPILE_DEFINITIONS not picked up

Hi all, if I do something like this, ADD_EXECUTABLE(myprog myprog.cpp) SET_PROPERTY(TARGET myprog APPEND PROPERTY COMPILE_DEFINITIONS "DEF1;DEF2" ) then the two macros DEF1 and DEF2 will be defined at compilation. However, if I switch to the corresponding CUDA setup,

Re: [CMake] Only install one component in cpack

Hi Tonka, You should read the doc here: https://cmake.org/cmake/help/v3.5/module/CPackComponent.html for the ZIP generator you should set(CPACK_ARCHIVE_COMPONENT_INSTALL ON) this is necessary because archive generator are "MONOLITHIC" by default. set(CPACK_COMPONENTS_GROUPING IGNORE) with this

[CMake] Only install one component in cpack

Hey, I want to create a zip file with only one component in it. Installers like nsis respect the CPACK_COMPONENTS_ALL settings, but the zip generator ignores it. Can I do that? Alternatively I would like to split every component into a single zip file, I know that it is possible but I forgot

Re: [CMake] Problems running npm-based tests on Windows

As demonstrated here https://github.com/QIICR/dcmqi/pull/79, the problem is resolved when .cmd versions of the commands are used. On Wed, Aug 24, 2016 at 1:10 PM, Andrey Fedorov wrote: > Hi, > > we are running ctest's on appveyor using npm-installed packages. >

Re: [CMake] trouble with find_package

I've never even used a Mac, so I am afraid I can't help you there. But I would assume there's a setting somewhere in the editor to enable/disable replacing straight quotes with curly ones. Petr On 24 August 2016 at 18:22, Cotton Candy wrote: > Hi Petr, > Indeed