Re: [cmake-developers] Tag signature with expired key

2016-12-12 Thread Alan W. Irwin
Speculation: the key was renewed locally, but those things have not been uploaded to the keyservers. Hi Eike: The explanation was similar to your above speculation but not quite. :-) I had not refreshed my local keyring from the keyservers recently. When I did that refresh (inspired by your

Re: [cmake-developers] Tag signature with expired key

2016-12-12 Thread Rolf Eike Beer
Am Montag, 12. Dezember 2016, 17:26:08 schrieb Alan W. Irwin: > Hi Brad: > > I attempted to verify a recent tag on the release branch with the > following results: > > software@raven> git tag --verify v3.7.1 > object db3499df5d06ab2cacc61e9f7720a33456aeafe4 > type commit > tag v3.7.1 > tagger

[cmake-developers] Tag signature with expired key

2016-12-12 Thread Alan W. Irwin
Hi Brad: I attempted to verify a recent tag on the release branch with the following results: software@raven> git tag --verify v3.7.1 object db3499df5d06ab2cacc61e9f7720a33456aeafe4 type commit tag v3.7.1 tagger Brad King 1480522722 -0500 CMake 3.7.1 gpg: Signature made

Re: [cmake-developers] Local target aliases

2016-12-12 Thread Egor Pugin
> If your trees are so huge or import so many other third-party projects that > name collisions are a problem They are. I'm predicting possible collisions, but it's ok for now. > ... ExternalProject. Not much suitable. --- Ok, I'll try to do some workarounds. Thanks for the replies. On 12

Re: [cmake-developers] CPackProductbuild Scripts

2016-12-12 Thread clinton
- On Dec 12, 2016, at 9:51 AM, Harry Mallon ha...@codexdigital.com wrote: > Hello, > > I am messing around with the CPackProductbuild stuff to try to port over what > we > had before. Currently it support undocumented options > "CPACK_PREFLIGHT_SCRIPT", "CPACK_POSTFLIGHT_SCRIPT", >

Re: [cmake-developers] Local target aliases

2016-12-12 Thread Brad King
On 12/12/2016 11:35 AM, Egor Pugin wrote: > So, the original proposal is to make ALIAS & OBJECT targets local. And > explicit GLOBAL keyword will make them global again. An OBJECT library is just like any other target as far as the generated build system is concerned, so it needs a globally

[cmake-developers] CPackProductbuild Scripts

2016-12-12 Thread Harry Mallon
Hello, I am messing around with the CPackProductbuild stuff to try to port over what we had before. Currently it support undocumented options "CPACK_PREFLIGHT_SCRIPT", "CPACK_POSTFLIGHT_SCRIPT", "CPACK_PREFLIGHT__SCRIPT" and "CPACK_POSTFLIGHT__SCRIPT". It looks like these are also supported

Re: [cmake-developers] Local target aliases

2016-12-12 Thread Egor Pugin
So, the original proposal is to make ALIAS & OBJECT targets local. And explicit GLOBAL keyword will make them global again. On 12 December 2016 at 18:37, Brad King wrote: > On 12/10/2016 04:13 PM, Egor Pugin wrote: >> Is it possible to add GLOBAL option as for

Re: [cmake-developers] Local target aliases

2016-12-12 Thread Brad King
On 12/10/2016 04:13 PM, Egor Pugin wrote: > Is it possible to add GLOBAL option as for INTERFACE/IMPORTED targets > (lib/exe)? The GLOBAL option is only available with an IMPORTED target: https://cmake.org/cmake/help/v3.7/command/add_library.html#imported-libraries Non-imported targets are