The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15539
==
Reported By:Mathieu Malaterre
Assigned To:
On 04/28/2015 05:54 PM, Alan W. Irwin wrote:
notice there is no mention of such ordering in the CMake documentation
of cmake_minimum_required() and project(), and I hope you will be
willing to fix that documentation
Help: Document that cmake_minimum_required should be called first
On 04/29/2015 09:46 AM, Tamás Kenéz wrote:
The example for CMP0054 does not show how critical the policy is since
the result is the same in both cases (NEW and OLD policies).
I think it would be more educational to show an example when the
policy does make a difference.
Applied with revised
Please find attached the patch concerning the description per component,
with the associated documentation, based on
75b0e1679c39ca824a4c49d9e1a2ae2b5f04ae06.
Applied with minor changes
- added component text from your other patch
- changed CPACK_DEBIAN_PACKAGE_DESCRIPTION documentation to
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15543
==
Reported By:Felix Geyer
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15542
==
Reported By:Felix Geyer
Assigned To:
Alan W. Irwin wrote:
On 2015-04-28 14:54-0700 Alan W. Irwin wrote:
Also, a spurious warning is probably not that big a deal, but if you
think the incorrect order of project(...) before
cmake_minimum_required(...) could lead to more serious issues now or
in the future as Platform code gets
Domen Vrankar wrote:
Usually what I do in such cases is
- commit each patch separately to git
- when I have to change one of them I just save commit messages, call
git format-patch -5 HEAD where 5 is the amount of commits to the one
that I wish to change
- use git reset --soft HEAD^ to undo
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15545
==
Reported By:Felix Geyer
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15544
==
Reported By:Stephen Kelly
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15547
==
Reported By:Daniel Schepler
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15546
==
Reported By:Steven Petsche
Assigned To:
Hello dear developers!
Recently we learned the good news about the release QtIFW 2.0:
http://blog.qt.io/blog/2015/04/07/qt-installer-framework-2-0-released
And I too was delighted at once. But then I was faced with an unstable work of
the installer on Windows and it upset me.
I think QtIFW
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15540
==
Reported By:Orion Poplawski
Assigned To:
Le 28/04/15 12:23, Domen Vrankar a écrit :
Hi,
Sorry for not replying sooner.
Attachement ...
From b1e65486c99ff1023310e3c42fd509fc22e0575d Mon Sep 17 00:00:00 2001
From: Raffi Enficiaud raffi.enfici...@mines-paris.org
Date: Wed, 29 Apr 2015 16:43:50 +0200
Subject: [PATCH] CPackDEB: adding
Le 28/04/15 12:23, Domen Vrankar a écrit :
Hi,
Sorry for not replying sooner.
Please find attached a patch for the reworked documentation. I tried to make
the doc more consistent with the CPackRPM (doc right after the variable
declaration and options afterwards).
I also put links for the
16 matches
Mail list logo