Re: [cmake-developers] How to use cmake::SetCacheArgs(...)?

Am 30.11.2016 19:10 schrieb "Brad King" : > If you want to ensure a fresh one-step configuration then always remove > CMakeCache.txt and CMakeFiles/ before configuring. People are really attached to their configuration and get upset when creator runs CMake. Creator running

[CMake] A trouble in using cmake for xcode

hi dear: I have a trouble in using cmake.I try to find a way to resolve that for a long time, but finally get no results. I attempt to create an ios application imessage extension by cmake but i can't find a suitable command. So i contact you for some suggestion. Look forward for your

Re: [CMake] FindMPI

OK, upon more careful reading of the documentation for FindMPI, and realizing that I am using CMake 3.6 not 3.7 I have adjusted my approach to be consistent with the documentation and your suggestions. I don't know if the documentation actually needs expanding upon... I think I just failed to

[Cmake-commits] CMake branch, master, updated. v3.7.1-702-g7b6f6d9

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

Re: [CMake] Using a header only library that links uses Objective-C headers

> > You don't compile a header only library That's what I thought but this is my first time dealing with header only libraries. Thanks for clearing up that confusion. What you need is compiling the sources using it as Objective C. > Which is a matter of adding target_compile_options( PRIVATE >

[cmake-developers] [ANNOUNCE] CMake 3.7.1 available for download

We are pleased to announce that CMake 3.7.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.7.1 since 3.7.0: Ben

[CMake] [ANNOUNCE] CMake 3.7.1 available for download

We are pleased to announce that CMake 3.7.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.7.1 since 3.7.0: Ben

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

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.7.1 has been created at 26aac2d7f704e19fc5f8b8958716944b2a1d502a (tag) tagging

Re: [cmake-developers] VS2015 /Zc:inline

On 11/30/2016 02:13 PM, Serti Ayoub wrote: > Sorry, I think it's an error on VS2015 documentation. They pretend that, > I quote "By default, this option is off (*/Zc:inline-*)." However the > default value is */Zc:inline* Actually that documentation is for the MSVC compiler itself (`cl`), and it

Re: [cmake-developers] VS2015 /Zc:inline

On 11/30/2016 02:24 PM, Serti Ayoub wrote: > Ok, Thank you. I will check CMake 3.7.2 when released. I updated the MR to include the changes for the v140 toolset as well. You should be able to try the next nightly binary that appears here: * https://cmake.org/files/dev/?C=M;O=D -Brad --

[Cmake-commits] CMake branch, next, updated. v3.7.0-1461-g5ae1cea

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

Re: [cmake-developers] VS2015 /Zc:inline

Ok, Thank you. I will check CMake 3.7.2 when released. -Ayb 2016-11-30 19:17 GMT+00:00 Brad King : > On 11/30/2016 02:13 PM, Serti Ayoub wrote: > > Sorry, I think it's an error on VS2015 documentation. > > Okay. My

Re: [cmake-developers] VS2015 /Zc:inline

On 11/30/2016 02:13 PM, Serti Ayoub wrote: > Sorry, I think it's an error on VS2015 documentation. Okay. My previous response crossed with this one. > Is the any way to remove this from CFlags, It seems that > > set_target_properties(${ProjectTarget} PROPERTIES COMPILE_FLAGS >

Re: [cmake-developers] VS2015 /Zc:inline

On 11/30/2016 01:37 PM, Serti Ayoub wrote: > Here: > https://github.com/Kitware/CMake/blob/1b592b6458ce033b04ba2aa0ee4cf5ace0fd042c/Source/cmVS141CLFlagTable.h#L174 > > I think it need also an entry : { "RemoveUnreferencedCodeData", "Zc:inline-", > "", "false", 0} Yes, thanks: *

Re: [cmake-developers] VS2015 /Zc:inline

Sorry, I think it's an error on VS2015 documentation. They pretend that, I quote "By default, this option is off (*/Zc:inline-*)." However the default value is */Zc:inline* https://msdn.microsoft.com/en-us/library/dn642448.aspx Is the any way to remove this from CFlags, It seems that >

[Cmake-commits] CMake branch, next, updated. v3.7.0-1459-g7080e8b

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

Re: [cmake-developers] VS2015 /Zc:inline

Hello, Here: https://github.com/Kitware/CMake/blob/1b592b6458ce033b04ba2aa0ee4cf5ace0fd042c/Source/cmVS141CLFlagTable.h#L174 I think it need also an entry : { "RemoveUnreferencedCodeData", "Zc:inline-", "", "false", 0 } What do you think ? -Ayb 2016-11-30 18:12 GMT+00:00 Brad King

[Cmake-commits] CMake branch, next, updated. v3.7.0-1457-gb98f80e

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1455-g39ee174

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1453-g093053c

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

Re: [cmake-developers] VS2015 /Zc:inline

On 11/30/2016 12:29 PM, Serti Ayoub wrote: > I'm using CMake 3.6 to generate VS2015 solution/projects. > I found that cmake automatically add /Zc:inline for all projects > configuration which make some of my symbols non-visible in release mode. I'm not aware of any code in CMake that does that.

Re: [cmake-developers] How to use cmake::SetCacheArgs(...)?

On 11/30/2016 12:06 PM, Tobias Hunger wrote: > start over with a clean cache since the compiler changed (which is correct). > > After cmake::Configure(...) returns values some of the values are gone > again. E.g. CMAKE_BUILD_TYPE changed back from "Debug" to "". > > Is this expected behavior?

[cmake-developers] VS2015 /Zc:inline

Hello, I'm using CMake 3.6 to generate VS2015 solution/projects. I found that cmake automatically add /Zc:inline for all projects configuration which make some of my symbols non-visible in release mode. https://msdn.microsoft.com/en-us/library/dn642448(v=vs.120).aspx Is there any policy for

[CMake] [SUGGESTION] Add %ONLY alternative for configure_file command

Relative issue: https://gitlab.kitware.com/cmake/cmake/issues/16471 Uncomfortable now create templates for file which themselves use `@` (the dog) to separate the variables. For example, this occurs in QtIFW scripts for components and installer (for example, see

[cmake-developers] How to use cmake::SetCacheArgs(...)?

Hello CMake developers, I am trying to pass a number of arguments to cmake server-mode's configure command. The exact call is: [== "CMake Server" ==[ { "cacheArguments": [ "-DCMAKE_BUILD_TYPE:STRING=Debug", "-DCMAKE_CXX_COMPILER:STRING=/usr/lib/ccache/bin/g++",

Re: [CMake] Using a header only library that links uses Objective-C headers

You don't compile a header only library (unless you're talking about precompiled headers, which I think you don't). What you need is compiling the sources using it as Objective C. Which is a matter of adding target_compile_options( PRIVATE "-ObjC") on the target with the sources if I remember

[CMake] Using a header only library that links uses Objective-C headers

First time poster so I hope I get the etiquette right. I'm a novice CMake user and I've never come across the type of issue before. I'm trying to figure out how to use this cross platform header only dialog library in my project. https://github.com/guillaumechereau/noc When using this on OSX, it

[Cmake-commits] CMake branch, next, updated. v3.7.0-1451-ge2bc5a3

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1449-g0182855

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-725-gf2035cb

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1447-gbc8c145

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

[Cmake-commits] CMake branch, release, updated. v3.7.0-24-gdb3499d

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1445-g44b706e

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

[Cmake-commits] CMake branch, release, updated. v3.7.0-23-gf75d936

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1442-g7b67436

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-723-gafe7d5f

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-719-g29b37dd

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-721-g12823fa

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-1439-g36406b4

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-715-g2036639

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-701-gd5ab04f

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-699-g8224545

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-696-g4288708

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-717-ga53a2f1

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

[Cmake-commits] CMake branch, master, updated. v3.7.0-705-g32e95a7

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