[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-127-g33f74dc

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

Re: [cmake-developers] CMake daemon-mode

Hi Brad, I just rebased this branch on top of current master and pushed it. There were some conflicts. Best Regards, Tobias On Mon, Jun 13, 2016 at 4:16 PM, Brad King wrote: > On 06/10/2016 12:31 PM, Tobias Hunger wrote: >> I did try to do the changes you requested. The

[cmake-developers] daemon-mode: Infrastructure

Hello, one important piece of feedback from the daemon-mode: Project structure discussion is that we need a policy to remove old code again. So I thought I should write up a bit about the infrastructure and versioning support of the daemon-mode branch I am working on. Basic Assumptions:

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-302-g41ecb26

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-298-gc563a2b

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

Re: [cmake-developers] daemon-mode: Project structure

On 06/13/2016 03:12 PM, Stephen Kelly wrote: > I suggest switching gears and designing the initial protocol handshake and > version negotiation, and come back to this buildsystem description part of > the protocol later. > > Designing the how versioning the protocol works can include design and

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc2-292-g86b38f8

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc2-126-g1bafa0b

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

Re: [cmake-developers] Problems when generating xcarchive from within Xcode

On 06/13/2016 02:58 PM, Roman Wüger wrote: > I have successfully configured a project with CMake 3.5.2 so it > creates a valid Release and Debug *.app bundle which runs on iOS. > However if I build an archive in Xcode with "Product->Archive" > then the app bundle seems not complete under >

Re: [CMake] [cmake-developers] Problems when generating xcarchive from within Xcode

On 06/13/2016 02:58 PM, Roman Wüger wrote: > I have successfully configured a project with CMake 3.5.2 so it > creates a valid Release and Debug *.app bundle which runs on iOS. > However if I build an archive in Xcode with "Product->Archive" > then the app bundle seems not complete under >

Re: [cmake-developers] daemon-mode: Project structure

Tobias Hunger wrote: >> * Designing a protocol like this is hard (and not fast) > > We have been discussing this for about two years now. That's a misleading thing to say. Time since an effort or discussion started has never been a guideline for when something is ready for CMake master. > I

[cmake-developers] [ANNOUNCE] CMake 3.6.0-rc2 now ready for testing!

I am proud to announce the second CMake 3.6 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.6 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.6/release/3.6.html Some of the more significant

[CMake] [ANNOUNCE] CMake 3.6.0-rc2 now ready for testing!

I am proud to announce the second CMake 3.6 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.6 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.6/release/3.6.html Some of the more significant

[Cmake-commits] CMake annotated tag, v3.6.0-rc2, created. v3.6.0-rc2

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 annotated tag, v3.6.0-rc2 has been created at bb5ad4202a91fcf07b0f1ac3c2708be8dea409c3 (tag) tagging

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-310-g1f06758

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

[CMake] Problems when generating xcarchive from within Xcode

Hello, I have successfully configured a project with CMake 3.5.2 so it creates a valid Release and Debug *.app bundle which runs on iOS. However if I build an archive in Xcode with "Product->Archive" then the app bundle seems not complete under

[cmake-developers] Problems when generating xcarchive from within Xcode

Hello, I have successfully configured a project with CMake 3.5.2 so it creates a valid Release and Debug *.app bundle which runs on iOS. However if I build an archive in Xcode with "Product->Archive" then the app bundle seems not complete under

Re: [cmake-developers] Review request: extract-cmMessenger branch

On 06/13/2016 04:22 PM, Brad King wrote: > On 06/11/2016 08:14 AM, Stephen Kelly wrote: >> Thanks for your thorough review! I think I've fixed the errors I >> introduced while rebasing now. >> >> I'm not completely certain that the gymnastics I do with the >> cmListFileBacktrace in the parser in

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-308-g3e90ac3

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-305-gce3b106

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-302-g18a6666

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

Re: [CMake] GCC: -std=g++14 vs -std=c++14

On Mon, 13 Jun 2016 18:40:59 +0200 Sylvain Joubert wrote: > Le 13/06/2016 11:36, Patrick Boettcher a écrit : > > Hi list, > > > > I'm using gcc for a c++14-based project. > > > > To have cmake add the corresponding -std=-flag I'm setting > > > >set_property(TARGET

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-144-g8d80c89

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-300-g8bdf697

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

[Cmake-commits] CMake branch, release, updated. v3.6.0-rc1-20-g9f3546b

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

Re: [cmake-developers] Questions about coding conventions

On Mon, Jun 13, 2016 at 16:14:51 +0200, Daniel Pfeifer wrote: > On Mon, Jun 13, 2016 at 2:09 PM, Ben Boeckel wrote: > > Usually NULL means "unset". See properties, > > variable values, etc. As an output, any place which doesn't care should > > already be using

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-298-gd42d169

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-296-g91cb438

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-293-gff55f7c

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

Re: [CMake] GCC: -std=g++14 vs -std=c++14

Le 13/06/2016 11:36, Patrick Boettcher a écrit : Hi list, I'm using gcc for a c++14-based project. To have cmake add the corresponding -std=-flag I'm setting set_property(TARGET PROPERTY CXX_STANDARD 14) This makes that when gcc is used cmake adds -std=gnu++14 . How can I make it set

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-291-g5ec42ea

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

Re: [CMake] how to compile single source file with debug options?

Hi all On 10/06/16 14:05, Sergey Spiridonov wrote: > To debug and fix our applications/libraries we often need to recompile > single source file in a debug mode. With the our current build system it > is as simple, as touching a file an starting make with debug option. It > will then recompile

Re: [cmake-developers] [PATCH] Allow LIB_SUFFIX be used as find path

Hi Christian, Thanks for working on this. On 06/12/2016 05:59 AM, Christian Schmidbauer wrote: > A similar idea has already been suggested in #10287 Yes. > and is required for bug #15594. That issue appears unrelated. Did you typo the number? > Help/command/find_library.rst

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-285-gf635582

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

[Cmake-commits] CMake branch, release, updated. v3.6.0-rc1-19-g023e2a1

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-142-g0514fa2

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-282-g20e110d

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-279-gfba0b6b

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

Re: [cmake-developers] cmCacheManager related changes

On 06/10/2016 02:13 PM, Stephen Kelly wrote: > Things which do change in such a way should be accessed through > cmState::Snapshot, or classes which depend on cmState::Snapshot such as > cmState::Directory for directory properties, or some day cmState::Target for > target properties. That way

Re: [cmake-developers] CMake daemon-mode

On 06/10/2016 12:31 PM, Tobias Hunger wrote: > I did try to do the changes you requested. The branch is here: > > https://github.com/hunger/CMake/commits/compileflags Thanks. I'm about to go on travel but should hopefully be able to look at that again when I return. -Brad -- Powered by

Re: [cmake-developers] Questions about coding conventions

On 06/10/2016 05:43 PM, Daniel Pfeifer wrote: >> Please look at documenting this in CONTRIBUTING.rst once we resolve >> this discussion. > > ok. +1 to Steve's suggestion of putting it in cmake-developer(7). >>> So far it is pretty consistent. But how to name free functions and >>> macros? I

Re: [cmake-developers] Dogfooding: clang-tidy, include-what-you-use, link-what-you-use

On 06/12/2016 05:47 PM, Daniel Pfeifer wrote: > I have set up a dashboard build where all three mechanisms are enabled: [snip] > I have already drastically reduced the number of clang-tidy warnings > in the last weeks. I am currently experimenting with > include-what-you-use and will push some

Re: [cmake-developers] Questions about coding conventions

On Mon, Jun 13, 2016 at 2:09 PM, Ben Boeckel wrote: > On Mon, Jun 13, 2016 at 00:03:29 +0200, Daniel Pfeifer wrote: >> Can you show an example? To be clear: We are looking for a function, >> that has a code path for `str == NULL` and a *different* codepath for >> `str[0]

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-277-g1e49316

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-140-g473634e

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc1-267-g0d3c95e

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-135-g4e66ca1

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-127-g3b14a4b

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-132-g18e00ac

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-125-g941fbe3

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-123-gff1cce4

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-114-g7ce354d

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc1-119-g6b0ab86

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

[CMake] [ANNOUNCE] CMake Issue Tracker Moved

Hi Folks, CMake issue tracking is now hosted on Kitware's GitLab instance: https://gitlab.kitware.com/cmake/cmake/issues The old mantis issue tracker will remain available as a read-only reference. All CMake issues from that tracker have been migrated to the new CMake Issues page with their

Re: [cmake-developers] Questions about coding conventions

On Mon, Jun 13, 2016 at 00:03:29 +0200, Daniel Pfeifer wrote: > Can you show an example? To be clear: We are looking for a function, > that has a code path for `str == NULL` and a *different* codepath for > `str[0] = '\0'`. As input to functions? Usually NULL means "unset". See properties,

[CMake] GCC: -std=g++14 vs -std=c++14

Hi list, I'm using gcc for a c++14-based project. To have cmake add the corresponding -std=-flag I'm setting set_property(TARGET PROPERTY CXX_STANDARD 14) This makes that when gcc is used cmake adds -std=gnu++14 . How can I make it set -std=c++14 instead? Background: my problem is the

Re: [CMake] Testing commands that are intended to fail

John P. Hartmann writes: > Excuse me for asking a no doubt obvious question. > > The test case (objlink is the executable): > > add_test( nullobjlink ) > > The log: > > Output: > -- > Positional argument(s)