Re: [cmake-developers] FindRuby doesn't find 64-bit Ruby on Windows

2015-02-06 Thread Brad King
On 02/06/2015 03:29 PM, Michael Smith wrote: The 64-bit ruby library names are: * lib/libx64-mscvrt-ruby210-static.a * lib/libx64-mscvrt-ruby210.dll.a * bin/x64-mscvrt-ruby210.dll I've attached a patch that adds x64- prefixed lookup Thanks for working on this. Some of the other find

[cmake-developers] FindRuby doesn't find 64-bit Ruby on Windows

2015-02-06 Thread Michael Smith
It appears FindRuby fails to find 64-bit Ruby on Windows. Debug output is -- FindRuby.cmake debug -- _RUBY_POSSIBLE_EXECUTABLE_NAMES: ruby1.9;ruby19;ruby;ruby2.1;ruby21;ruby2.0;ruby20;ruby1.8;ruby18 -- _RUBY_POSSIBLE_LIB_NAMES:

Re: [cmake-developers] FindRuby doesn't find 64-bit Ruby on Windows

2015-02-06 Thread Michael Smith
Non-prefixed names shouldn't be used for 64-bit architectures. The only major releases with 64-bit support are 2.0.0 and 2.1.5, and both use the x64- prefix. New patch attached. Follow-up question: Why doesn't FindRuby use Config::CONFIG['LIBRUBY'], 'LIBRUBY_A', 'LIBRUBY_SO' to search for libs?

Re: [cmake-developers] FindRuby doesn't find 64-bit Ruby on Windows

2015-02-06 Thread Ben Boeckel
On Fri, Feb 06, 2015 at 15:00:50 -0800, Michael Smith wrote: Non-prefixed names shouldn't be used for 64-bit architectures. The only major releases with 64-bit support are 2.0.0 and 2.1.5, and both use the x64- prefix. New patch attached. What about AArch64? Follow-up question: Why doesn't

Re: [cmake-developers] FindRuby doesn't find 64-bit Ruby on Windows

2015-02-06 Thread Michael Smith
On Fri, Feb 6, 2015 at 4:42 PM, Ben Boeckel ben.boec...@kitware.com wrote: On Fri, Feb 06, 2015 at 15:00:50 -0800, Michael Smith wrote: Non-prefixed names shouldn't be used for 64-bit architectures. The only major releases with 64-bit support are 2.0.0 and 2.1.5, and both use the x64-

Re: [cmake-developers] msbuild VisualStudioEdition value (was: Fix for Windows Store warning APPX1901...)

2015-02-06 Thread Robert Goulet
Gilles? Any advices about this one? Thanks! -Original Message- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, February 3, 2015 3:12 PM To: Robert Goulet; Gilles Khouzam Cc: cmake-developers@cmake.org Subject: Re: msbuild VisualStudioEdition value (was: Fix for Windows

Re: [cmake-developers] Fortran detection, issue 9220

2015-02-06 Thread Ben Boeckel
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 years! The workaround from Eigen works fine

[cmake-developers] GCC5 and C++11 ABI

2015-02-06 Thread Ben Boeckel
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/ --Ben -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: