On 02/10/2015 07:56 AM, Robert Maynard wrote:
So we can safely presume that the new features listed at
https://gcc.gnu.org/gcc-5/changes.html will be the what gcc 5.0 will
ship with?
That's how I read things.
On Mon, Feb 9, 2015 at 11:18 PM, Orion Poplawski or...@cora.nwra.com wrote:
On
On 02/09/2015 12:17 PM, Ruslan Baratov via cmake-developers wrote:
This patch let do the check that exit code is 0, i.e. install_name_tool
exits successfully.
Applied with minor refactoring:
BundleUtilities: Teach fixup_bundle to check install_name_tool result
On 02/06/2015 09:10 PM, Michael Smith wrote:
On Fri, Feb 6, 2015 at 4:42 PM, Ben Boeckel wrote:
Doesn't work for cross-compiles.
FindRuby is already querying ruby for libdir. How does that work
for cross-compiles but using some of the other config doesn't?
That one doesn't work either, but
On 02/06/2015 06:00 PM, Michael Smith wrote:
New patch attached.
Applied, thanks:
FindRuby: Fix finding 64-bit Ruby on Windows
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e5ef9271
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
So we can safely presume that the new features listed at
https://gcc.gnu.org/gcc-5/changes.html will be the what gcc 5.0 will
ship with?
On Mon, Feb 9, 2015 at 11:18 PM, Orion Poplawski or...@cora.nwra.com wrote:
On 02/09/2015 11:08 AM, Ben Boeckel wrote:
On Mon, Feb 09, 2015 at 11:09:32
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15400
==
Reported By:Ruslan Baratov
Assigned To:
On Tue, Feb 10, 2015 at 17:15:33 -0800, Alan W. Irwin wrote:
As the originator (almost 6 years ago) of this bug report I am still
very much interested in a fundamental solution to give a WARNING
message rather than an error if there is any issue with a compiler.
This patch makes it only an
On 2015-02-06 10:21-0500 Ben Boeckel wrote:
On Fri, Feb 06, 2015 at 07:01:55 +0100, Christoph Grüninger wrote:
would you mind to tackle issue 9220 enable_language( OPTIONAL)
signature does not work correctly? It's a shame that CMake cannot
properly detect optional Fortran for more than 5
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15401
==
Reported By:Wojciech A. Koszek
Assigned To:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15399
==
Reported By:Florent
Assigned To:
On Fri, Feb 06, 2015 at 13:15:45 -0500, Ben Boeckel wrote:
Looks like compiler_feature_detection will need to normalize the
_GLIBCXX_USE_CXX11_ABI preprocessor define as well:
http://developerblog.redhat.com/2015/02/05/gcc5-and-the-c11-abi/
Followup (LWN comments will likely have
I've finally had some time to read over the Tests section, and it is a
bit overwhelming.
I'm going to describe the use cases for my patch and perhaps you can
give me some guidance on adding an actual test.
There are three, maybe four use cases:
1) native rpm (e.g. x86_64)
2) noarch rpm (a noarch
On 02/07/2015 05:23 PM, Nuno Sucena Almeida wrote:
---
bootstrap | 8
1 file changed, 8 insertions(+)
Thanks, applied:
bootstrap: Add --sphinx-qthelp option to enable qthelp doc generation
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=85fd62ee
-Brad
--
Powered by
On 02/09/2015 05:14 PM, Domen Vrankar wrote:
To get around this problem I thought about wrapping the entire script with:
cmake_policy(PUSH)
cmake_policy(VERSION 3.1)
cmake_policy(POP)
Would this be an acceptable solution?
That is currently the intended way to do it.
There was once some
14 matches
Mail list logo
