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
https://cmake.org/cmake/help/v3.6/release/
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 @vari
Hello, Brad!
Some time ago I created two merge request:
https://gitlab.kitware.com/cmake/cmake/merge_requests/26
https://gitlab.kitware.com/cmake/cmake/merge_requests/27
I received some comments from Ben Boeckel and resolve them.
Please consider the possibility of a merge it.
--
Regards,
Konst
I have a concern with generating package configs:
1 It seems to contain absolute path, so not really portable with git.
2 It does not respect the naming of imported targets with `::`. As you
can see here:
https://cmake.org/cmake/help/git-master/manual/cmake-developer.7.html#a-sample-find-module
T
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
--
Powere
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 wrote:
>> The target property
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 late
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 So
>
> The library builds using CMake and rather than using more code to find
> itself, it should instead create a package configuration file which
> contains the exact information CMake needs to use its install tree. See
> the docs:
>
>
> https://cmake.org/cmake/help/latest/manual/cmake-packages.7.ht
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
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 typically use that.
Otherwi
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 doc
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 che
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
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
>> > missing overrides.
>> >
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:
https://cmake.org/gitweb?p=stage/cma
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,
--
A
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
> > http
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 a
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,
T
20 matches
Mail list logo