Re: [cmake-developers] FindBoost.cmake cannot find some libraries when cross-compiling

2014-10-23 Thread Guillaume Papin
Please find the patch attached to this email. Let me know if anything is wrong. Best, Guillaume On 10/16/2014 05:09 PM, Chuck Atkins wrote: Guillaume, Please see CONTRIBUTING.rst in the top level of the CMake source tree. If you can please create and post a patch against cmake master then

[cmake-developers] [TEST REQUEST] CPack IFW generator on OSX

2014-10-23 Thread Konstantin Podsvirov
Hello developers! Can anybody test IFW generator on Mac? Regards, Konstantin Podsvirov -- 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

Re: [cmake-developers] [TEST REQUEST] CPack IFW generator on OSX

2014-10-23 Thread Sean McBride
On Thu, 23 Oct 2014 16:45:36 +0400, Konstantin Podsvirov said: Can anybody test IFW generator on Mac? Probably... What is it? :) How would I test it? If you can give me clear instructions, I can update one or more of my dashboards to test it. Cheers, --

Re: [cmake-developers] Support of codesign

2014-10-23 Thread Brad King
On 10/21/2014 11:44 AM, Clinton Stimpson wrote: Because the design of this Bundle generator is not consistent with the rest of the CPack generators, you don't have this same chance, and the only way to do customization is to keep adding patches like yours. Is this something that should be

Re: [cmake-developers] [TEST REQUEST] CPack IFW generator on OSX

2014-10-23 Thread Konstantin Podsvirov
Hi Sean! 23.10.2014, 19:09, Sean McBride s...@rogue-research.com: On Thu, 23 Oct 2014 16:45:36 +0400, Konstantin Podsvirov said: Can anybody test IFW generator on Mac? Probably... What is it? :) How would I test it? If you can give me clear instructions, I can update one or more of my

Re: [cmake-developers] Support of codesign

2014-10-23 Thread Clinton Stimpson
On Thursday, October 23, 2014 11:13:15 AM Brad King wrote: On 10/21/2014 11:44 AM, Clinton Stimpson wrote: Because the design of this Bundle generator is not consistent with the rest of the CPack generators, you don't have this same chance, and the only way to do customization is to keep

Re: [cmake-developers] Support of codesign

2014-10-23 Thread Adam Strzelecki
Let me put my 2¢. I have feeling that we are mixing up signing (install) packages, such as .pkg (OSX) or .msi (Windows), with signing bundles .app or whatever OSX binaries (that can keep signature inside macho). I think that CPack should be responsible of signing only what it creates. Since

Re: [cmake-developers] Support of codesign

2014-10-23 Thread Brad King
On 10/23/2014 12:21 PM, Clinton Stimpson wrote: Actually, the design is intentional -- that is, it has the feature of creating the application bundle for you, which involves handling for icons, Info.plist, and now the proposed code signing. Alternatively, we have handling for icons and

[cmake-developers] Fwd: Re: Severe behavioural change regressions in release branch

2014-10-23 Thread Bill Hoffman
FYI, a conversation on the KDE mailing list. Forwarded Message Subject: Re: Severe behavioural change regressions in release branch Date: Fri, 24 Oct 2014 10:11:02 +1300 From: Ben Cooksley bcooks...@kde.org Reply-To: KDE build system (cmake) kde-buildsys...@kde.org To:

Re: [cmake-developers] Fwd: Re: Severe behavioural change regressions in release branch

2014-10-23 Thread Ben Boeckel
[ Adding Ben Cooksley to the CC list; feel free to reply privately and I'll forward to the list if you keep getting rejected from it. ] Hi, It would appear that CMake 3.0 to 3.1 introduces a colossal change in behaviour. This change totally breaks all KDE projects which use

Re: [CMake] [CPACK] [RPM] Support of %preun and %postun

2014-10-23 Thread Domen Vrankar
2014-10-23 1:57 GMT+02:00 Luc J. Bourhis luc_j_bour...@mac.com: Am I missing something or there is no equivalent of CPACK_RPM_PRE_INSTALL_SCRIPT_FILE to specify %preun or %postun? The variables are missing in documentation but they exist. For %preun you can set

Re: [CMake] Is this the proper way to define a package config?

2014-10-23 Thread Johannes Zarl
Hi, Assuming you are not a boost developer / your changes won't be upstreamed, then creating a BoostConfig.cmake file won't do you much good. If someone wants to use your project, he/she will have to patch the locally installed boost version to include a BoostConfig.cmake file. You might want

[CMake] Definiting output extension for cross-compilation

2014-10-23 Thread Emmanuel Blot
Hi, How to tell CMake to use '.o' output object file (instead of the Windows' .obj forced alternative) when cross-compiling ? SET (CMAKE_SYSTEM_NAME Generic) ... SET (CMAKE_C_OUTPUT_EXTENSION .o) has no effect from a project file. forcing SET (UNIX 1) does work, but this is a terrible

[CMake] Concatenating lists back to string

2014-10-23 Thread Domen Vrankar
Hi, I am trying to convert string to list and back with string(REPLACE) and it doesn't work as expected (tested with cmake 2.8.12 on Ubuntu 14.04 and main branch in git on Ubuntu 14.10). cmake_minimum_required( VERSION 2.8.12 ) project(test_list) set(str_1 abc.def.ghi) message(str_1: ${str_1})

Re: [CMake] Concatenating lists back to string

2014-10-23 Thread Petr Kmoch
Hi Domen. This is what helps me reason about it: A string with a ';' in it is a list. An unqouted ';' separates arguments to CMake commands. string(REPLACE ...) simply concatenates all of its 'input' parameters. So, when you expand ${list_1} in the last line, it will simply replace in the

[CMake] Controlling the verbosity in CTest scripts

2014-10-23 Thread Pere Mato Vila
Hi, I am running a CTest script in our continuous and nighty integration builds and tests scheduled by Jenkins. The test suit contains more than 1000 tests with a lot of output. Jenkins has a nice way to digest the test output and present it. What I would like to have is also the output of

Re: [CMake] Is this the proper way to define a package config?

2014-10-23 Thread Robert Dailey
Thanks for the reply! Basically the boost library I have is precompiled and in my own unique structure. I do not plan to distribute the CMake scripts I write, they are for personal / internal usage only. You suggested a find module, but will this also generate a custom target for boost? That's

[CMake] Can't build using NINJA with ITKDCMTK/ITKIODCMTK turned on.

2014-10-23 Thread Williams, Norman K
A couple of years ago, with massive help from Brad King, I managed to get an embedded ExternalProject build of DCMTK embedded into ITK/Modules/ThirdParty. This was workable, because the CMake dependencies were explicitly set up such that the DCMTK libraries depended on the ExternalProject DCMTK

Re: [CMake] [ITK-dev] Can't build using NINJA with ITKDCMTK/ITKIODCMTK turned on.

2014-10-23 Thread Bill Hoffman
On 10/23/2014 1:32 PM, Williams, Norman K wrote: I have no idea how this could be resolved, except to remove the internal DCMTK build and require USE_SYSTEM_DCMTK=ON. Does anyone have a better idea. The other option is to build this without external project and use add_subdirectory like we do

Re: [CMake] [ITK-dev] Can't build using NINJA with ITKDCMTK/ITKIODCMTK turned on.

2014-10-23 Thread Brad King
On 10/23/2014 01:32 PM, Williams, Norman K wrote: it fails immediately because the targets in Modules/IO/DCMTK depend on non-existent DCMTK libraries. This cannot be solved cleanly without addressing these issues: https://github.com/martine/ninja/issues/760#issuecomment-46540858

Re: [CMake] [ITK-dev] Can't build using NINJA with ITKDCMTK/ITKIODCMTK turned on.

2014-10-23 Thread Williams, Norman K
Yeah that¹s the problem right there. I would have no problem with including DCMTK in the distro. On 10/23/14, 1:03 PM, Brad King brad.k...@kitware.com wrote: On 10/23/2014 01:32 PM, Williams, Norman K wrote: it fails immediately because the targets in Modules/IO/DCMTK depend on non-existent

[CMake] Pass on Unix Signals (ctrl+c)?

2014-10-23 Thread digitalriptide
I have a number of tests configured in my CMakeLists.txt file, a few of which need to do some cleanup after running or if they are interrupted If I run make tests, and then send a signal (via ctrl+c, for example), however, these signals are not passed on to the test. Is it possible to configure

[CMake] CMake, Xcode, and Intel Fortran?

2014-10-23 Thread digitalriptide
In the past I was able to generate Xcode projects that contained Fortran files via `cmake -gXcode ..` and CMake would pick up the Intel Fortran compiler. This behavior seems to have changed recently, however. Has anyone else experienced this problem and/or found a workaround? Is this is an issue

Re: [CMake] Pass on Unix Signals (ctrl+c)?

2014-10-23 Thread digitalriptide
Alternatively, what signal does CMake use to halt tests? Than you! On Thu, Oct 23, 2014 at 2:16 PM, digitalriptide digitalript...@gmail.com wrote: I have a number of tests configured in my CMakeLists.txt file, a few of which need to do some cleanup after running or if they are interrupted If

[CMake] The new cmake.org web site

2014-10-23 Thread David Cole via CMake
The new CMake web site looks fantastic! Even on my phone... Kudos to everybody involved in making it look pretty after all these years of, well, ahem, looking slightly less pretty... However, on this page: http://www.cmake.org/developer-resources/ The Dashboard icon is a broken link. 404.

[Cmake-commits] CMake branch, master, updated. v3.0.2-2105-g2a668e2

2014-10-23 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 2a668e20da7ba6ae380eb44219f285f13fd34981 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.2-2108-gb2a7f60

2014-10-23 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via b2a7f60a4660ced5892e47eb1e7dd560313c340c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.2-2167-g26b5708

2014-10-23 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via 26b5708919e7784cfa9abd6b5f9eace499e3a5ce (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.2-2111-g21c2dd8

2014-10-23 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, master has been updated via 21c2dd842b4323ac754c3bc76c6b8af25aa26fcc (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.2-2171-gaf134fe

2014-10-23 Thread Brad King
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via af134fe2c3653881024f3cdc643adf4c5f994821 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.2-2176-gb9c0886

2014-10-23 Thread Stephen Kelly
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via b9c08862c69eb2ffe4bc0751381b864db9607537 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.0.2-2180-gbf034ea

2014-10-23 Thread Chuck Atkins
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project CMake. The branch, next has been updated via bf034eac301d0242c5fe673bb062bbea95ac73f5 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.0.2-2112-gfbc2a38

2014-10-23 Thread Kitware Robot
20141023) +set(CMake_VERSION_PATCH 20141024) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake