[Cmake-commits] CMake branch, master, updated. v3.6.0-rc4-275-g2c75997

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

Re: [CMake] [ANNOUNCE] CMake 3.6.0-rc4 now ready for testing!

Am 29. Juni 2016 21:30:40 MESZ, schrieb Robert Maynard : >I am proud to announce the fourth CMake 3.6 release candidate. > >Sources and binaries are available at: > https://cmake.org/download/ > >Documentation is available at: > https://cmake.org/cmake/help/v3.6 >

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

I am proud to announce the fourth CMake 3.6 release candidate. Sources and binaries are available at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.6 Release notes appear below and are also published at

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

I am proud to announce the fourth CMake 3.6 release candidate. Sources and binaries are available at: https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.6 Release notes appear below and are also published at

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

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-rc4 has been created at c5888b14ff23f075f73d3bf0933c5029459236f0 (tag) tagging

[CMake] how to ctest with pre- and -post processing

Hi, Is it possible to have a ctest which involves preprocessing as well as postprocessing. The code I want to test is myCode.exe, which writes an output file OUTPUT. Measure for success is a comparison of OUTPUT against REFERENCE data file. Currently, I use two add_tests:

Re: [CMake] How do you handle recursive dependencies in CMake

On 29 June 2016 at 05:08, Raymond Wan wrote: > I agree that what we're observing is a problem, but I don't think it is that big. I must admit I am mixing a bit of my own situation here and trying to think about the most general case. It's just there is a missing bit in the

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-644-g7eff8e7

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

Re: [CMake] CMAKE_C_COMPILE_OBJECT vs

Looks like this was just a change in CMake 3.4. Updated to latest, and everything is working. > On Jun 28, 2016, at 5:19 PM, Sam Cristall wrote: > > I'm trying to implement a cross compilation wrapper and hit a snag with > CMAKE_C_COMPILE_OBJECT. I've found that on

Re: [cmake-developers] adding FindJsonCpp

On Wed, Jun 29, 2016 at 17:36:45 +0200, Farbos a wrote: > I have a concern with generating package configs: > > 1 It seems to contain absolute path, so not really portable with git. The actual config files are generated at build time, not committed to the source control (template files with

[Cmake-commits] CMake branch, release, updated. v3.6.0-rc3-17-gdd71ec2

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc3-291-g108c665

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

Re: [cmake-developers] [CMake] [iOS] What is the correct way to add resources to an XCode project

On Wed, Jun 29, 2016 at 16:48:10 +0200, Roman Wüger wrote: > I know because I wrote this ticket. Ah. I didn't check the Mantis side. > I thought this was "closed/want fixed" because of the implementation > for RESOURCE a few days ago. Hmm. I don't see that. Do you have a link? --Ben --

Re: [CMake] [cmake-developers] [iOS] What is the correct way to add resources to an XCode project

On Wed, Jun 29, 2016 at 16:48:10 +0200, Roman Wüger wrote: > I know because I wrote this ticket. Ah. I didn't check the Mantis side. > I thought this was "closed/want fixed" because of the implementation > for RESOURCE a few days ago. Hmm. I don't see that. Do you have a link? --Ben --

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-642-g4c20291

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

Re: [cmake-developers] [CMake] [iOS] What is the correct way to add resources to an XCode project

Thanks Ben, I know because I wrote this ticket. I thought this was "closed/want fixed" because of the implementation for RESOURCE a few days ago. Regards Roman > Am 29.06.2016 um 14:52 schrieb Ben Boeckel : > >> On Tue, Jun 28, 2016 at 23:01:56 +0200, Roman Wüger

Re: [CMake] [cmake-developers] [iOS] What is the correct way to add resources to an XCode project

Thanks Ben, I know because I wrote this ticket. I thought this was "closed/want fixed" because of the implementation for RESOURCE a few days ago. Regards Roman > Am 29.06.2016 um 14:52 schrieb Ben Boeckel : > >> On Tue, Jun 28, 2016 at 23:01:56 +0200, Roman Wüger

Re: [cmake-developers] Script to update liblzma from upstream.

On 06/28/2016 05:24 PM, Daniel Pfeifer wrote: > I have attached a patch that adds a script to update liblzma from > upstream (closely modeled after the other update scripts). I am not > sure how these kinds of scripts need to be run. > > We currently have a copy of liblzma version 5.0.5. The

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-630-g4e7bb44

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc3-289-g7808ba0

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-622-gf723860

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-609-g567fdf0

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

[Cmake-commits] CMake branch, release, updated. v3.6.0-rc3-16-ge34c554

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-619-g4edd80f

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-611-gb89f500

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

Re: [cmake-developers] adding FindJsonCpp

On 06/29/2016 09:40 AM, Chuck Atkins wrote: > Given these issues, how about we "bring back" the FindJsonCpp module, > and alter it to explicitly look for the package config first. > It's still in the Modules tree and is actually used by CMake to build > itself, it'd just not installed. It is in

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-607-gd4342c4

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-605-ga10cf4e

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

Re: [cmake-developers] Script to update liblzma from upstream.

On Wed, Jun 29, 2016 at 09:06:25 -0400, Brad King wrote: > If there is a developer mailing list I typically use that. > Otherwise I use kwrobot. Ah, makes sense. --Ben -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc3-284-g8d79375

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-601-g50c0cf8

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-599-ge0a1084

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc3-282-g5e2c638

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

[Cmake-commits] CMake branch, master, updated. v3.6.0-rc3-280-gcb93dc0

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

Re: [cmake-developers] Script to update liblzma from upstream.

On 06/29/2016 09:02 AM, Ben Boeckel wrote: >> +readonly ownership="liblzma upstream " > > This should probably use kwro...@kitware.com as the email. The oddball I > see in the repo now is libarchive. Brad, why is that not kwrobot? If there is a developer mailing list I

Re: [cmake-developers] Script to update liblzma from upstream.

On Tue, Jun 28, 2016 at 23:24:22 +0200, Daniel Pfeifer wrote: > I have attached a patch that adds a script to update liblzma from > upstream (closely modeled after the other update scripts). I am not > sure how these kinds of scripts need to be run. Thanks! Looks like Brad hadn't imported the

Re: [CMake] [cmake-developers] [iOS] What is the correct way to add resources to an XCode project

On Tue, Jun 28, 2016 at 23:01:56 +0200, Roman Wüger wrote: > The target property RESOURCE does only allow files but no directories. There's an open issue for this: https://gitlab.kitware.com/cmake/cmake/issues/14743 --Ben -- Powered by www.kitware.com Please keep messages on-topic and

Re: [cmake-developers] [CMake] [iOS] What is the correct way to add resources to an XCode project

On Tue, Jun 28, 2016 at 23:01:56 +0200, Roman Wüger wrote: > The target property RESOURCE does only allow files but no directories. There's an open issue for this: https://gitlab.kitware.com/cmake/cmake/issues/14743 --Ben -- Powered by www.kitware.com Please keep messages on-topic and

Re: [cmake-developers] adding FindJsonCpp

On Wed, Jun 29, 2016 at 11:02:30 +0200, Farbos a wrote: > I would like to add a find module: FindJsonCpp.cmake that I attached. > the library github: https://github.com/open-source-parsers/jsoncpp. > > This library allows JSON manipulation. It's used by more than one > person and I think it could

Re: [cmake-developers] Please apply patch from https://github.com/hunger/CMake/commits/for-upstream to master

On Wed, Jun 29, 2016 at 10:17 AM, Tobias Hunger wrote: > On Mi, 2016-06-29 at 09:54 +0200, Rolf Eike Beer wrote: >> Am 2016-06-29 09:35, schrieb Tobias Hunger: >> > Hello Brad, >> > >> > I currently get more than 2000 warnings when building cmake master, all >> > about >> >

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-595-g724554c

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

[Cmake-commits] CMake branch, next, updated. v3.6.0-rc3-593-g0462af8

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

Re: [cmake-developers] Patch for CM_OVERRIDE

On Wed, Jun 29, 2016 at 7:15 AM, Roman Wüger wrote: > Hello, > > I've attached a patch for the CM_OVERRIDE commit Hi Roman, I added "override" to the destructor on purpose. The intent is to make the check fail in Visual Studio 10. See the commit message here:

[cmake-developers] adding FindJsonCpp

Hi, I would like to add a find module: FindJsonCpp.cmake that I attached. the library github: https://github.com/open-source-parsers/jsoncpp. This library allows JSON manipulation. It's used by more than one person and I think it could useful to add a find module for this library. Thanks, --

Re: [cmake-developers] Please apply patch from https://github.com/hunger/CMake/commits/for-upstream to master

On Mi, 2016-06-29 at 09:54 +0200, Rolf Eike Beer wrote: > Am 2016-06-29 09:35, schrieb Tobias Hunger: > > Hello Brad, > > > > I currently get more than 2000 warnings when building cmake master, all  > > about > > missing overrides. > > > > Could you please take the fix warning patch from > >

Re: [cmake-developers] Please apply patch from https://github.com/hunger/CMake/commits/for-upstream to master

Am 2016-06-29 09:35, schrieb Tobias Hunger: Hello Brad, I currently get more than 2000 warnings when building cmake master, all about missing overrides. Could you please take the fix warning patch from https://github.com/hunger/CMake/commits/for-upstream and apply it to master? That fixes

[cmake-developers] Please apply patch from https://github.com/hunger/CMake/commits/for-upstream to master

Hello Brad, I currently get more than 2000 warnings when building cmake master, all about missing overrides. Could you please take the fix warning patch from https://github.com/hunger/CMake/commits/for-upstream and apply it to master? That fixes all those pesky override warnings. Best Regards,