Re: [cmake-developers] [PATCH] User may now specify toolset through CMake GUI

2015-02-16 Thread Clinton Stimpson
On Monday, February 16, 2015 11:35:47 AM Brad King wrote: On 02/15/2015 03:27 PM, rcdailey.li...@gmail.com wrote: From: Robert Dailey rcdai...@gmail.com The -T parameter to CMake may now be specified through QtDialog (cmake-gui) via a new text field in the first-time configure wizard

Re: [cmake-developers] [PATCH] User may now specify toolset through CMake GUI

2015-02-16 Thread Brad King
On 02/15/2015 03:27 PM, rcdailey.li...@gmail.com wrote: From: Robert Dailey rcdai...@gmail.com The -T parameter to CMake may now be specified through QtDialog (cmake-gui) via a new text field in the first-time configure wizard (below the generator chooser). Thanks for working on this. I

Re: [cmake-developers] [PATCH] User may now specify toolset through CMake GUI

2015-02-16 Thread Robert Dailey
Fair points, I will make the changes. What is the recommended practice for updating patches on mailing lists? With pull requests it's easy because it picks up my changes I push to my branch automatically. I think if I push another patch to the mailing list it will start another email thread,

Re: [cmake-developers] [ANNOUNCE] CMake 3.2.0-rc1 now ready for testing!

2015-02-16 Thread Orion Poplawski
On 02/13/2015 01:12 PM, Robert Maynard wrote: I am proud to announce that CMake 3.2 has entered the release candidate stage. We're getting a fair number of test failures on Fedora Rawhide (with gcc 5 c++11): The following tests FAILED: 25 - FindPackageTest (Failed) 27 -

Re: [cmake-developers] [PATCH] User may now specify toolset through CMake GUI

2015-02-16 Thread Brad King
On 02/16/2015 11:59 AM, Robert Dailey wrote: What is the recommended practice for updating patches on mailing lists? With pull requests it's easy because it picks up my changes I push to my branch automatically. I think if I push another patch to the mailing list it will start another email

Re: [cmake-developers] GCC5 and C++11 ABI (was: CMake 3.2.0-rc1 now ready for testing)

2015-02-16 Thread Brad King
On 02/16/2015 12:27 PM, Orion Poplawski wrote: We're getting a fair number of test failures on Fedora Rawhide (with gcc 5 c++11): It builds fine on F22 which also has gcc 5, but not the c++11 ABI, so that seems like the likely culprit. To see if this has anything to do with the way CMake

Re: [cmake-developers] KWSys patches

2015-02-16 Thread Domen Vrankar
I'll get the KWSys patch through. Once it is integrated into CMake then you can rebase the CMake part of the change on that. However, please revise the logic in the KWSys patch to avoid using exceptions. I've noticed that exceptions are not used but was not certain how else to handle this

Re: [cmake-developers] Extracting target metadata, IDE integration

2015-02-16 Thread Aleix Pol
On Sat, Feb 14, 2015 at 1:02 PM, Stephen Kelly steve...@gmail.com wrote: Aleix Pol wrote: Hi guys, It's been since August with this. I understand we're all busy but this step is important for KDevelop as well as for other IDE's and I wouldn't like this to rot. Please, let's keep it moving

Re: [cmake-developers] KWSys patches

2015-02-16 Thread Brad King
On 02/16/2015 02:47 PM, Domen Vrankar wrote: I've noticed that exceptions are not used but was not certain how else to handle this FYI, the proposed GetCanonicalPath already exists in KWSys as SystemTools::GetRealPath. It returns the unchanged path on error. That could be extended to take an

Re: [cmake-developers] [PATCH] VS Fortran project file: Fix mismatch between OutputDirectory and OutputFile

2015-02-16 Thread Brad King
On 02/14/2015 03:56 PM, Vincent Newsum wrote: -\t\t\tOutputDirectory=\ configName \\n; +\t\t\tOutputDirectory=\ target.GetDirectory(configName) \\n; Thanks. The OutputFile is computed differently for different target types. We also need to encode the value for XML.

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

2015-02-16 Thread Orion Poplawski
On 02/16/2015 11:07 AM, Brad King wrote: On 02/16/2015 12:27 PM, Orion Poplawski wrote: We're getting a fair number of test failures on Fedora Rawhide (with gcc 5 c++11): It builds fine on F22 which also has gcc 5, but not the c++11 ABI, so that seems like the likely culprit. To see if this

Re: [cmake-developers] Extracting target metadata, IDE integration

2015-02-16 Thread Alexander Neundorf
On Monday, February 16, 2015 21:31:45 Aleix Pol wrote: On Sat, Feb 14, 2015 at 1:02 PM, Stephen Kelly steve...@gmail.com wrote: Aleix Pol wrote: Hi guys, It's been since August with this. I understand we're all busy but this step is important for KDevelop as well as for other IDE's and I

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

2015-02-16 Thread Orion Poplawski
On 02/16/2015 02:48 PM, Brad King wrote: On 02/16/2015 04:26 PM, Orion Poplawski wrote: On 02/16/2015 11:07 AM, Brad King wrote: To see if this has anything to do with the way CMake itself is compiled, please add this to the end of the bootstrap command line: -- -DCMAKE_C_STANDARD=90

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

2015-02-16 Thread Brad King
On 02/16/2015 04:26 PM, Orion Poplawski wrote: On 02/16/2015 11:07 AM, Brad King wrote: To see if this has anything to do with the way CMake itself is compiled, please add this to the end of the bootstrap command line: -- -DCMAKE_C_STANDARD=90 -DCMAKE_CXX_STANDARD=98 That does indeed

Re: [cmake-developers] KWSys patches

2015-02-16 Thread Brad King
On 02/15/2015 03:04 PM, Domen Vrankar wrote: I tried to register to http://review.source.kitware.com so that I would be able to commit patches to KWSys repository but after I put in my OpenID I got a Not Found error. I'll be in touch off-list about this. How can I contribute this patch?