[cmake-developers] Bad error message when a package could not be found - make find_package() not search config files by default

2012-02-16 Thread Alexander Neundorf
Hi, when I use a Find-module to search for a package, I get a nice error message if the package could not be found. If I use find_package(Foo) and rely on Config-mode, cmake produces an error message which doesn't help the user: ~/src/extra-cmake-modules/example/b$ make rebuild_cache Running

Re: [cmake-developers] Support for imported targets in CMAKE_REQUIRED_LIBRARIES

2012-02-16 Thread Brad King
On 2/16/2012 6:32 AM, Alexander Neundorf wrote: Done, and pushed to stage. I added the prefix cmake_ to the function, and added a test for it. Looks good, thanks. However now that I look at the end result I realize that the functionality is not specific to CMAKE_REQUIRED_LIBRARIES at all. It

Re: [cmake-developers] Support for imported targets in CMAKE_REQUIRED_LIBRARIES

2012-02-16 Thread Alexander Neundorf
On Thursday 16 February 2012, Brad King wrote: On 2/16/2012 6:32 AM, Alexander Neundorf wrote: Done, and pushed to stage. I added the prefix cmake_ to the function, and added a test for it. Looks good, thanks. However now that I look at the end result I realize that the functionality

Re: [cmake-developers] Bad error message when a package could not be found - make find_package() not search config files by default

2012-02-16 Thread Brad King
On 2/16/2012 8:19 AM, Alexander Neundorf wrote: Comments, objections ? The entire point of find_package's interface is that the caller does not need to care how the package is found, and the actual method used for the find can change under the hood. Ideally every package would provide a

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread Brad King
On 2/16/2012 10:15 AM, Alexander Neundorf wrote: On Thursday 16 February 2012, Brad King wrote: In hindsight that name was poorly chosen. I'd really like to see package in the name because they are package configuration files. Otherwise there is no indication it has anything to do with

Re: [cmake-developers] Bad error message when a package could not be found - make find_package() not search config files by default

2012-02-16 Thread Alexander Neundorf
On Thursday 16 February 2012, Brad King wrote: On 2/16/2012 8:19 AM, Alexander Neundorf wrote: Comments, objections ? The entire point of find_package's interface is that the caller does not need to care how the package is found, and the actual method used for the find can change under the

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread Alexander Neundorf
On Thursday 16 February 2012, Brad King wrote: On 2/16/2012 10:15 AM, Alexander Neundorf wrote: On Thursday 16 February 2012, Brad King wrote: In hindsight that name was poorly chosen. I'd really like to see package in the name because they are package configuration files. Otherwise

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread Brad King
On 2/16/2012 10:48 AM, Alexander Neundorf wrote: 5) configure_package_config_file() + write_basic_package_version_file() So, 5) ? Looks good. Thanks. -Brad -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please

Re: [cmake-developers] Bad error message when a package could not be found - make find_package() not search config files by default

2012-02-16 Thread Brad King
On 2/16/2012 10:30 AM, Alexander Neundorf wrote: In any of the above modes the error message can be more explicit. It is up to the author of the project to choose to do this. I do not want it to be required. Here we disagree. I think it should be required, to avoid the impression finding

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread David Cole
On Thu, Feb 16, 2012 at 10:52 AM, Brad King brad.k...@kitware.com wrote: On 2/16/2012 10:48 AM, Alexander Neundorf wrote: 5) configure_package_config_file(**) + write_basic_package_version_** file() So, 5) ? Looks good. Thanks. -Brad -- Powered by www.kitware.com Visit other

[cmake-developers] FYI: Cross compiling ideas...

2012-02-16 Thread Alexander Neundorf
Hi, just FYI some input on what people would like to have when cross compiling. Like uploading executables to the target in try_run(), installing to a target using something like scp, etc. Alex -- Forwarded Message -- Date: Thursday 16 February 2012, 14:32:21 From: Thomas

Re: [cmake-developers] target_include_directories branch in stage

2012-02-16 Thread David Cole
Pushed down the queue again... I'll get to it soon. There are a handful of minor changes that I still need to make first. On Thu, Feb 16, 2012 at 8:20 AM, Stephen Kelly steve...@gmail.com wrote: David Cole wrote: Excellent : thanks very much for trying it out. I'll try to get this first

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread Brad King
On 2/16/2012 1:24 PM, Alexander Neundorf wrote: Actually I expected I would prefer this over the fixed names, but now that I've done it and look at what Config.cmake.in file I have to write, I think I liked the previous version with the fixed names (CONFIG_HELPER) better. I think it was easier

Re: [cmake-developers] ninja broken on windows?

2012-02-16 Thread Peter Kümmel
On 16.02.2012 04:51, Bill Hoffman wrote: On 2/15/2012 5:52 PM, Peter Kümmel wrote: In summary: - use the CMakeLists.txt from https://github.com/syntheticpp/ninja/tree/cmake - on Windows use ninja from https://github.com/syntheticpp/ninja/tree/token-splitter and wait and see

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread Brad King
On 2/16/2012 3:29 PM, Eric Noulard wrote: What are you targeting? install-time i.e. make install usage? package install time prodduced with cpack usage? package install time NOT produced with cpack usage? a subset of this? The goal is a FooConfig.cmake file for make install time but that

Re: [cmake-developers] ninja broken on windows?

2012-02-16 Thread Bill Hoffman
On 2/16/2012 2:57 PM, Peter Kümmel wrote: They are not interested. There is another patch in the pipeline but with this the current generator doesn't work. Use the official ninja and drop Win atm. Bummer. I am most interested in windows. Would love to stop using gmake... Seems like they

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread Eric Noulard
2012/2/16 Brad King brad.k...@kitware.com: On 2/16/2012 3:29 PM, Eric Noulard wrote: What are you targeting? install-time i.e. make install usage? package install time prodduced with cpack usage? package install time NOT produced with cpack usage? a subset of this? The goal is a

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread David Cole
On Thu, Feb 16, 2012 at 3:52 PM, Eric Noulard eric.noul...@gmail.comwrote: 2012/2/16 Brad King brad.k...@kitware.com: On 2/16/2012 3:29 PM, Eric Noulard wrote: What are you targeting? install-time i.e. make install usage? package install time prodduced with cpack usage? package

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread Brad King
On 2/16/2012 4:13 PM, David Cole wrote: On Thu, Feb 16, 2012 at 3:52 PM, Eric Noulard eric.noul...@gmail.com mailto:eric.noul...@gmail.com wrote: I'm not convinced, yet I'll have to try with the example provided by Alex by adding proper CPack usage in it. Currently I see in

Re: [cmake-developers] ninja broken on windows?

2012-02-16 Thread Peter Kümmel
On 16.02.2012 21:38, Bill Hoffman wrote: On 2/16/2012 2:57 PM, Peter Kümmel wrote: They are not interested. There is another patch in the pipeline but with this the current generator doesn't work. Use the official ninja and drop Win atm. Bummer. I am most interested in windows. Would love

Re: [cmake-developers] ninja broken on windows?

2012-02-16 Thread Richard Wackerbarth
What are we trying to accomplish here? I have set up 3 of my machines (1 each MacOSX, FreeBSD, and Linux --- like my housekeeper, I don't do Windows) to submit nightly builds using the Ninja generator. That will test the impact of changes in the generator. But it appears that we may also need

Re: [cmake-developers] ninja broken on windows?

2012-02-16 Thread David Cole
On Thu, Feb 16, 2012 at 5:08 PM, Richard Wackerbarth rich...@nfsnet.orgwrote: What are we trying to accomplish here? 2 things: (1) Keep the CMake ninja generator working with the changing state of the CMake code base (primary) (2) Understanding what version of ninja works good on all the

Re: [cmake-developers] ninja broken on windows?

2012-02-16 Thread Bill Hoffman
On 2/16/2012 5:19 PM, David Cole wrote: On Thu, Feb 16, 2012 at 5:08 PM, Richard Wackerbarth rich...@nfsnet.org mailto:rich...@nfsnet.org wrote: What are we trying to accomplish here? 2 things: (1) Keep the CMake ninja generator working with the changing state of the CMake code base

[cmake-developers] Modifying RPATH feature to run tests uninstalled

2012-02-16 Thread Stephen Kelly
Hi there, One of the macros we have in KDE creates shell scripts to initialize environment variables needed on various platforms so that tests can be run before installation. If RPATH is enabled, the scripts are not needed, but RPATH is sometimes disabled, so the scripts are the solution to

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread Alexander Neundorf
On Thursday 16 February 2012, Brad King wrote: On 2/16/2012 1:24 PM, Alexander Neundorf wrote: Actually I expected I would prefer this over the fixed names, but now that I've done it and look at what Config.cmake.in file I have to write, I think I liked the previous version with the fixed

[cmake-developers] Making GUI applications by default

2012-02-16 Thread Stephen Kelly
Hi there, Also in this thread one of the discussion topics was making CMake default to creating Gui-ready executables. That is, setting the WIN32_EXECUTABLE or MACOSX_BUNDLE property on the executable target. http://thread.gmane.org/gmane.comp.kde.devel.buildsystem/6961/focus=7005 By

Re: [cmake-developers] Making Config.cmake files easier to write

2012-02-16 Thread Eric Noulard
2012/2/16 Brad King brad.k...@kitware.com: On 2/16/2012 4:13 PM, David Cole wrote: On Thu, Feb 16, 2012 at 3:52 PM, Eric Noulard eric.noul...@gmail.com mailto:eric.noul...@gmail.com wrote:    I'm not convinced, yet I'll have to try with the example provided by Alex    by adding proper CPack

Re: [CMake] How to have a static/shared option in a Find script ?

2012-02-16 Thread Barth
Hello again, A short question about your proposal : Michael Hertling wrote (4) DIM_USE_STATIC decides if DIM_LIBRARIES receives DIM_STATIC_LIBRARY or DIM_SHARED_LIBRARY, and because DIM_LIBRARIES is not cached, it can be set anew each time FIND_PACKAGE(DIM ...) is called, so the

Re: [CMake] How to have a static/shared option in a Find script ?

2012-02-16 Thread Barth
Hi again, I have understood what you meant :) For records here is what I did : Thank you again for your supprot, Best regards, Barth -- View this message in context: http://cmake.3232098.n2.nabble.com/How-to-have-a-static-shared-option-in-a-Find-script-tp7287655p7291050.html Sent from the

Re: [CMake] How to have a static/shared option in a Find script ?

2012-02-16 Thread Barth
Hi again, I have understood what you meant :) For records here is what I did : # (1) Use FIND_LIBRARY() to look for the shared and the static library # and define DIM_SHARED_LIBRARY and DIM_STATIC_LIBRARY in the cache. find_library(DIM_STATIC_LIBRARY NAMES libdim.a PATHS $ENV{DIMDIR}

Re: [CMake] How to have a static/shared option in a Find script ?

2012-02-16 Thread Michael Hertling
On 02/16/2012 03:14 PM, Barth wrote: Hi again, I have understood what you meant :) Hhm, actually, I talked nonsense w.r.t. DIM_USE_STATIC. ;) For records here is what I did : # (1) Use FIND_LIBRARY() to look for the shared and the static library # and define DIM_SHARED_LIBRARY and

Re: [CMake] On WINDOWS, Is it Possible to build 64-bit and 32-bit Solutions in One Go?

2012-02-16 Thread John Drescher
On Thu, Feb 16, 2012 at 2:54 PM, Hashim Mir h...@rim.com wrote: Hi, This is what I am doing presently in order to compile both a 32-bit and a 64-bit version of my project: cmake.exe -G “Visual Studio 9 2008” #for x32 cmake.exe -G “Visual Studio 9 2008 Win64”   #for x64 Is

Re: [CMake] On WINDOWS, Is it Possible to build 64-bit and 32-bit Solutions in One Go?

2012-02-16 Thread John Drescher
On Thu, Feb 16, 2012 at 3:27 PM, John Drescher dresche...@gmail.com wrote: On Thu, Feb 16, 2012 at 2:54 PM, Hashim Mir h...@rim.com wrote: Hi, This is what I am doing presently in order to compile both a 32-bit and a 64-bit version of my project: cmake.exe -G “Visual Studio 9 2008”  

[CMake] message could not create named generator CodeBlocks -MinGW Makefiles

2012-02-16 Thread pasparis
Hello,I am trying to use CMake with codeblocks on windows, I created a simple project in the folder pCMakewhen I use the CMake interface I got the message:CMake Error: CMake was unable to find a build program corresponding to "MinGW Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need

[CMake] find both shared and static versions?

2012-02-16 Thread Dougal Sutherland
I have an application where I want to link some targets against shared versions of Boost and some against static versions. (I'd prefer shared in general, but I need to link against the static version of boost for my matlab mex interface, to avoid loading the different version of boost shipped by

[CMake] Doesn't anyone know how to get precompiled headers working under CMake for Visual Studio 2010?

2012-02-16 Thread david_bjornbak
My team has been using precompiled headers under CMake and Visual Studio 2008 for quite a while. Now we've switched to VS 2010, the cmake code we used to support precompiled headers is no longer working. The following is the code in question and we're just using set_source_files_properties

Re: [CMake] Doesn't anyone know how to get precompiled headers working under CMake for Visual Studio 2010?

2012-02-16 Thread John Drescher
On Thu, Feb 16, 2012 at 7:39 PM, david_bjorn...@agilent.com wrote: My team has been using precompiled headers under CMake and Visual Studio 2008 for quite a while.  Now we’ve switched to VS 2010,  the cmake code we used to support precompiled headers is no longer working. The following is

[Cmake-commits] CMake branch, next, updated. v2.8.7-2653-g29fe3cb

2012-02-16 Thread Rolf Eike Beer
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 29fe3cbd7d5cb34465203abd4e27dcbe12103bd2 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.7-2660-gd8d31a6

2012-02-16 Thread David Cole
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 d8d31a644abde62197ba3dad669420e87339a924 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.7-2662-gf08963b

2012-02-16 Thread Alexander Neundorf
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 f08963bf9baf9312ec01ecb8f4eb57486c27083f (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.7-2668-gffdef87

2012-02-16 Thread David Cole
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 ffdef8726313f88bcfc534f37a989db8c5b93c47 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.7-378-gd03606a

2012-02-16 Thread KWSys Robot
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 d03606a19cc05872baf23269ae8ec61d2e0719e8 (commit) from