Please find the patch attached to this email.
Let me know if anything is wrong.
Best,
Guillaume
On 10/16/2014 05:09 PM, Chuck Atkins wrote:
Guillaume,
Please see CONTRIBUTING.rst in the top level of the CMake source
tree. If you can please create and post a patch against cmake master
then
Hello developers!
Can anybody test IFW generator on Mac?
Regards,
Konstantin Podsvirov
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
On Thu, 23 Oct 2014 16:45:36 +0400, Konstantin Podsvirov said:
Can anybody test IFW generator on Mac?
Probably... What is it? :) How would I test it? If you can give me clear
instructions, I can update one or more of my dashboards to test it.
Cheers,
--
On 10/21/2014 11:44 AM, Clinton Stimpson wrote:
Because the design of this Bundle generator is not consistent with the rest
of
the CPack generators, you don't have this same chance, and the only way to do
customization is to keep adding patches like yours.
Is this something that should be
Hi Sean!
23.10.2014, 19:09, Sean McBride s...@rogue-research.com:
On Thu, 23 Oct 2014 16:45:36 +0400, Konstantin Podsvirov said:
Can anybody test IFW generator on Mac?
Probably... What is it? :) How would I test it? If you can give me clear
instructions, I can update one or more of my
On Thursday, October 23, 2014 11:13:15 AM Brad King wrote:
On 10/21/2014 11:44 AM, Clinton Stimpson wrote:
Because the design of this Bundle generator is not consistent with the
rest of the CPack generators, you don't have this same chance, and the
only way to do customization is to keep
Let me put my 2ยข. I have feeling that we are mixing up signing (install)
packages, such as .pkg (OSX) or .msi (Windows), with signing bundles .app or
whatever OSX binaries (that can keep signature inside macho).
I think that CPack should be responsible of signing only what it creates. Since
On 10/23/2014 12:21 PM, Clinton Stimpson wrote:
Actually, the design is intentional -- that is, it has the feature of
creating
the application bundle for you, which involves handling for icons,
Info.plist,
and now the proposed code signing. Alternatively, we have handling for icons
and
FYI, a conversation on the KDE mailing list.
Forwarded Message
Subject: Re: Severe behavioural change regressions in release branch
Date: Fri, 24 Oct 2014 10:11:02 +1300
From: Ben Cooksley bcooks...@kde.org
Reply-To: KDE build system (cmake) kde-buildsys...@kde.org
To:
[ Adding Ben Cooksley to the CC list; feel free to reply privately and
I'll forward to the list if you keep getting rejected from it. ]
Hi,
It would appear that CMake 3.0 to 3.1 introduces a colossal change in
behaviour. This change totally breaks all KDE projects which use
10 matches
Mail list logo
