Re: [cmake-developers] Fwd: [ANNOUNCE] CMake 3.1.2 Released

2015-02-10 Thread Orion Poplawski

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 02/09/2015 11:08 AM, Ben Boeckel wrote:


On Mon, Feb 09, 2015 at 11:09:32 -0500, Robert Maynard wrote:


We are pleased to announce that CMake 3.1.2 is now available for
download.




I'm getting this now building cmake 3.1.2 for Fedora Rawhide with gcc
5.0.0:

32: Detecting CXX compile features - done
32: Testing feature : cxx_aggregate_default_initializers
32: Configuring
32: CMake Error at CMakeLists.txt:70 (message):
32:   Feature cxx_aggregate_default_initializers expected not to work for
CXX
32:   GNU-5.0.0.
32:
32: Update the supported features or blacklist it.

32: Testing feature : cxx_relaxed_constexpr
32: Configuring
32: CMake Error at CMakeLists.txt:70 (message):
32:   Feature cxx_relaxed_constexpr expected not to work for CXX
GNU-5.0.0.
32:
32: Update the supported features or blacklist it.

32: Testing feature : cxx_variable_templates
32: Configuring
32: CMake Error at CMakeLists.txt:70 (message):
32:   Feature cxx_variable_templates expected not to work for CXX
GNU-5.0.0.
32:
32: Update the supported features or blacklist it.



Yeah, the feature tables will need to be updated. I use Rawhide at home
(was going to send an email about the tests as well) and was going to
look at updating it there. However, it is still a pre-release build of
GCC5, so we should probably just hold off on pushing something into
master until an official release is made.

--Ben



According to
https://fedoraproject.org/wiki/Changes/GCC5#Detailed_Description :

GCC 5 is currently in stage4 - prerelease state with only regression
bugfixes and documentation fixes allowed.

So I think it's reasonable time to start adapting to it.



--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA DivisionFAX: 303-415-9702
3380 Mitchell Lane  or...@cora.nwra.com
Boulder, CO 80301  http://www.cora.nwra.com



--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA DivisionFAX: 303-415-9702
3380 Mitchell Lane  or...@cora.nwra.com
Boulder, CO 80301  http://www.cora.nwra.com
--

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] BundleUtilities check exit code

2015-02-10 Thread Brad King
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
 http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=a27c13f4

Please verify that this version of the change still works for you.

Thanks,
-Brad
-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


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

2015-02-10 Thread Brad King
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 we shouldn't add more cases.

-Brad

-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


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

2015-02-10 Thread Brad King
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: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] Fwd: [ANNOUNCE] CMake 3.1.2 Released

2015-02-10 Thread Robert Maynard
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 -0500, Robert Maynard wrote:

 We are pleased to announce that CMake 3.1.2 is now available for
 download.



 I'm getting this now building cmake 3.1.2 for Fedora Rawhide with gcc
 5.0.0:

 32: Detecting CXX compile features - done
 32: Testing feature : cxx_aggregate_default_initializers
 32: Configuring
 32: CMake Error at CMakeLists.txt:70 (message):
 32:   Feature cxx_aggregate_default_initializers expected not to work for
 CXX
 32:   GNU-5.0.0.
 32:
 32: Update the supported features or blacklist it.

 32: Testing feature : cxx_relaxed_constexpr
 32: Configuring
 32: CMake Error at CMakeLists.txt:70 (message):
 32:   Feature cxx_relaxed_constexpr expected not to work for CXX
 GNU-5.0.0.
 32:
 32: Update the supported features or blacklist it.

 32: Testing feature : cxx_variable_templates
 32: Configuring
 32: CMake Error at CMakeLists.txt:70 (message):
 32:   Feature cxx_variable_templates expected not to work for CXX
 GNU-5.0.0.
 32:
 32: Update the supported features or blacklist it.


 Yeah, the feature tables will need to be updated. I use Rawhide at home
 (was going to send an email about the tests as well) and was going to
 look at updating it there. However, it is still a pre-release build of
 GCC5, so we should probably just hold off on pushing something into
 master until an official release is made.

 --Ben


 According to
 https://fedoraproject.org/wiki/Changes/GCC5#Detailed_Description :

 GCC 5 is currently in stage4 - prerelease state with only regression
 bugfixes and documentation fixes allowed.

 So I think it's reasonable time to start adapting to it.



 --
 Orion Poplawski
 Technical Manager 303-415-9701 x222
 NWRA/CoRA DivisionFAX: 303-415-9702
 3380 Mitchell Lane  or...@cora.nwra.com
 Boulder, CO 80301  http://www.cora.nwra.com
-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


[cmake-developers] [CMake 0015400]: fixup_bundle does not work on cpack stage

2015-02-10 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=15400 
== 
Reported By:Ruslan Baratov
Assigned To:
== 
Project:CMake
Issue ID:   15400
Category:   Modules
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2015-02-10 09:21 EST
Last Modified:  2015-02-10 09:21 EST
== 
Summary:fixup_bundle does not work on cpack stage
Description: 
fixup_bundle works as expected if cmake installs target, but not when cpack
creating a package.

Steps to Reproduce: 
Example with Visual Studio 12, Qt and NSIS generator (see attached
CMakeLists.txt and main.cpp):
1. cmake -H. -B_builds -GVisual Studio 12 2013 -DCMAKE_INSTALL_PREFIX=_install
-DCPACK_GENERATOR=NSIS
2. cmake --build _builds --config Release --target install
3. dependent Qt libraries installed in local _install directory:
  -- fixup_bundle: copying...
  -- 1/14: *NOT* copying '.../_install/bin/foo.exe'
  -- 2/14: copying '.../bin/Qt5Core.dll'
  -- 3/14: copying '.../bin/Qt5Gui.dll'
  -- 4/14: copying '.../bin/Qt5Widgets.dll'
  -- 5/14: copying '.../bin/icudt53.dll'
  -- 6/14: copying '.../bin/icuin53.dll'
  -- 7/14: copying '.../bin/icuuc53.dll'
  -- fixup_bundle: fixing...
  -- 8/14: fix-up not required on this platform '.../_install/bin/foo.exe'
  -- 9/14: fix-up not required on this platform '.../_install/bin/Qt5Core.dll'
  -- 10/14: fix-up not required on this platform '.../_install/bin/Qt5Gui.dll'
  -- 11/14: fix-up not required on this platform
'.../_install/bin/Qt5Widgets.dll'
  -- 12/14: fix-up not required on this platform '.../_install/bin/icudt53.dll'
  -- 13/14: fix-up not required on this platform '.../_install/bin/icuin53.dll'
  -- 14/14: fix-up not required on this platform '.../_install/bin/icuuc53.dll'
4. But not if cpack build installer:
   cd _builds
   cpack --verbose -C Release -GNSIS
  CPack Verbose: fixup_bundle: copying...
  CPack Verbose: 1/2: *NOT* copying
'.../_builds/_CPack_Packages/win32/NSIS/Foo-1.0.0-win32/bin/foo.exe'
  CPack Verbose: fixup_bundle: fixing...
  CPack Verbose: 2/2: fix-up not required on this platform
'.../_builds/_CPack_Packages/win32/NSIS/Foo-1.0.0-win32/bin/foo.exe'
  CPack Verbose: fixup_bundle: cleaning up...
  CPack Verbose: fixup_bundle: verifying...
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-02-10 09:21 Ruslan Baratov New Issue
2015-02-10 09:21 Ruslan Baratov File Added: CMakeLists.txt
==

-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


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

2015-02-10 Thread Ben Boeckel
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 error when Ninja detects a Fortran compiler
rule being written (which is where the actual incompatibility lies).

Other languages error out because CMake doesn't have *any* knowledge of
how to build them. Java is kinda-sorta there IIRC. I haven't used it
much, but I don't remember it feeling first-class.

 That capability is fundamentally important for projects like PLplot
 that support more than one different compiled computer language
 (PLplot supports the compiled languages Ada, C, C++, Fortran, D, and
 Java)

You might be interested in the first-class D support here where I've
been dabbling in some personal projects:

https://github.com/trentforkert/cmake

Other languages would need similar efforts to be fully supported. That
said, putting logic behind enable_language(OPTIONAL) would be nice.

--Ben
-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


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

2015-02-10 Thread Alan W. Irwin

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 years! The workaround
from Eigen works fine for me, but it's still embarrassing.

BTW, is there a way to disable the optional Fortran by a flag to CMake?
I couldn't find any...


Here is a commit which I haven't worked on for a while which delays the
error until you request an actual build of a Fortran object:

   
https://github.com/mathstuf/CMake/commit/880d783bf7fbd986b8a50a712e69ff40abbcfa07

While not the OPTIONAL signature, it is more accurate. Let me know how
it works for you.


Some additional comments for both Christoph and Ben:

This issue is for all language compilers, not just Fortran, and this
issue is orthogonal to the well-known lack of support for Fortran in
ninja.

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.
That capability is fundamentally important for projects like PLplot
that support more than one different compiled computer language
(PLplot supports the compiled languages Ada, C, C++, Fortran, D, and
Java) where the project developer's want users to at least have
partial functionality if say the Ada compiler does not work.  We do
have a workaround (see early comments in
http://public.kitware.com/Bug/view.php?id=9220 for details), but that
approach is inefficient (you have to check compilers twice), and
doesn't correctly propagate all the many different ways (e.g.,
environment variables, CMake cache variables) you can specify
compilers and compiler flags to the special small CMake test build
system used to check the compiler for each required compiled language.

The most recent comment (by Brad King) at
http://public.kitware.com/Bug/view.php?id=9220 states the
documentation has now been changed to state that OPTIONAL is a
placeholder (in enable_language) that does not work.
So at least OPTIONAL has now been clearly marked as defunct.

Brad also recommends an alternative approach to using OPTIONAL in
enable_language.  I haven't had a chance to look into that possibility
yet, but I will do so because an efficient and clean solution for
providing a soft landing when a compiler test fails is important for
the PLplot project.

Alan
__
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__
--

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[cmake-developers] [CMake 0015401]: Cmake Xcode project generation doesn't support Swift language

2015-02-10 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://public.kitware.com/Bug/view.php?id=15401 
== 
Reported By:Wojciech A. Koszek
Assigned To:
== 
Project:CMake
Issue ID:   15401
Category:   CMake
Reproducibility:always
Severity:   tweak
Priority:   low
Status: new
== 
Date Submitted: 2015-02-10 20:43 EST
Last Modified:  2015-02-10 20:43 EST
== 
Summary:Cmake Xcode project generation doesn't support Swift
language
Description: 
I successfully use CMake for Xcode project generation. So I run cmake -GXcode
followed by xcodebuild. It seems like right now cmake knows how to recognize .m
files, but doesn't know how to handle .swift files.

It would be great to teach it that.


Steps to Reproduce: 
Tested on MacOSX Yosemite with cmake installed from brew install cmake.

CMakeLists.txt 
cmake_minimum_required (VERSION 2.6)
project (sample)
add_executable(sample  ../sample.swift)

cmake -GXcode
[wkoszek-macbook:~/github/macb/obj] wkoszek% cmake -GXcode
-- Configuring done
-- Generating done
CMake Error: CMake can not determine linker language for target: sample
CMake Error: CMake can not determine linker language for target: sample
CMake Error: CMake can not determine linker language for target: sample
CMake Error: CMake can not determine linker language for target: sample
CMake Error: CMake can not determine linker language for target: sample
CMake Error: CMake can not determine linker language for target: sample
CMake Error: CMake can not determine linker language for target: sample
CMake Error: CMake can not determine linker language for target: sample
-- Build files have been written to: /Users/wkoszek/github/macb/obj



== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-02-10 20:43 Wojciech A. KoszekNew Issue
==

-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


[cmake-developers] [CMake 0015399]: cmake xml-escapes ; for visual studio generators resulting in malformed ignore default libraries

2015-02-10 Thread Mantis Bug Tracker

The following issue has been SUBMITTED. 
== 
http://www.cmake.org/Bug/view.php?id=15399 
== 
Reported By:Florent
Assigned To:
== 
Project:CMake
Issue ID:   15399
Category:   CMake
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
== 
Date Submitted: 2015-02-10 05:57 EST
Last Modified:  2015-02-10 05:57 EST
== 
Summary:cmake xml-escapes ; for visual studio generators
resulting in malformed ignore default libraries
Description: 
I have the following cmakelist : 

set_property(TARGET MyLibraryUsingFortranRt APPEND PROPERTY LINK_FLAGS
/NODEFAULTLIB:svml_disp.lib 
libifcoremt.lib
libcmt.lib
libcmtd.lib
libmmt.lib
libifport.lib)

this generates the following xml fragment with 3.1 (Visual 2010 generator) 
 
IgnoreSpecificDefaultLibrariessvml_disp.lib%3Blibifcoremt.lib%3Blibcmt.lib%3Blibcmtd.lib%3Blibmmt.lib%3Blibifport.lib;%(IgnoreSpecificDefaultLibraries)/IgnoreSpecificDefaultLibraries


(notice how ; got correctly escaped to %3B ! ) 

However for this specific filed VS expect to have ; present in the xml as it
is the case with 3.0 making it impossible to ignore several libraries. 





Additional Information: 
from my end-less researches, this is linked to 

http://www.cmake.org/Bug/view.php?id=15031

and most likely this commit : 
http://www.cmake.org/gitweb?p=cmake.git;a=commitdiff;h=8fa087ab
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-02-10 05:57 FlorentNew Issue
2015-02-10 05:57 FlorentFile Added:
VS_escaped_ignore_specific_libraries.PNG
==

-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


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

2015-02-10 Thread Ben Boeckel
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 interesting detail as well):

https://lwn.net/Articles/632734/

--Ben
-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [PATCH] CPackRPM: Fix cross-building rpms

2015-02-10 Thread Joshua Clayton
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 package should contain scripts, artwork, etc,
but no compiled code)
3) a non-native, but compatible rpm (e.g. building x86 on a multilib
x86_64 system)
4) incompatible cross-compiled package (e.g. building for arm or ppc)

in each case the way you know it worked is
a) make package successfully produces an rpm file
b) running rpm -qip my_rpm_file.my_arch.rpm returns a description of the rpm,
 including the line Architecture: my_arch

On Tue, Feb 3, 2015 at 11:50 PM, Domen Vrankar domen.vran...@gmail.com wrote:
 Add the --target argument to rpmbuild
 Do not add a BuildArch variable to the spec file for arch specific packages
 BuildArch causes rpm building to fail except for noarch packages

 I'm not too familiar with cross compilation problems so could you
 please also provide a simple test case to help with patch review?

 Thanks,
 Domen
-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] [PATCH] add --sphinx-qthelp command line argument to bootstrap script.

2015-02-10 Thread Brad King
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 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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


Re: [cmake-developers] old policies interfering with script provided by CPack

2015-02-10 Thread Brad King
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 discussion of trying to scope policies automatically
for modules within CMake, but currently it must be explicit.

-Brad

-- 

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 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers