[cmake-developers] [CMake 0013848]: Object_Library limitation import/export

The following issue has been SUBMITTED. == http://www.cmake.org/Bug/view.php?id=13848 == Reported By:Tomasz Majchrowski Assigned To:

Re: [cmake-developers] add_library(OBJECT) and AUTOMOC

On 01/14/2013 10:47 PM, Yury G. Kudryashov wrote: Pushed an updated branch with new commit messages. Could you push it to the repo, please? Done, thanks! -Brad -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

[cmake-developers] [CMake 0013849]: ExternalProject_Add works in a wrong way for DEPENDS property

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13849 == Reported By:Ivan Bednyakov Assigned To:

[cmake-developers] Review Request: Automatically link to libqtmain on Windows

Hi, Thanks for all the recent merges. We've reached the point where I only have a handful of topics left. I've just pushed qt4-autolink-qtmain to my gitorious clone https://gitorious.org/~steveire/cmake/steveires- cmake/commit/020b692e7becdc82eb68484abfa3069029b0c8b1

Re: [cmake-developers] Review Request: Automatically link to libqtmain on Windows

On 01/15/2013 03:20 PM, Stephen Kelly wrote: https://gitorious.org/~steveire/cmake/steveires- cmake/commit/020b692e7becdc82eb68484abfa3069029b0c8b1 https://gitorious.org/~steveire/cmake/steveires- cmake/commit/530209f7a6e3fd323ebd429e53c01d1eebee7480 I introduced a policy to link the

Re: [CMake] Magick++ trimming pixels that are not of background color (pixels same color on top and bottom of image)

Whoops, I accidentally sent this to the wrong mailing list! On Mon, Jan 14, 2013 at 3:38 AM, imagene...@gmail.com imagene...@gmail.comwrote: Forgot to specify the image: http://s1.postimage.org/a7r69yxsr/m_medium_bc.png On Mon, Jan 14, 2013 at 3:37 AM, imagene...@gmail.com

[CMake] Building multiple binaries from same source into one package

I'm looking for some pointers on how to go about to build multiple binaries (libraries for C, C++ C++11 e.g.) and then package them into a single package. Currently I'm using multiple out-of-source build directories (one for each platform) which works ok for build and test purposes (Makefile

Re: [CMake] retreiving the libraries the maven way?

CMake doesn't support this out of the box. For most library dependencies, it's not even possible to retrieve their version, because either the FindXYZ scripts aren't written properly, or because the library doesn't provide it in the first place. Every library and every Find script does things

[CMake] ADD_CUSTOM_TARGET

I am trying to build a project for Red-hat 6 which uses the following cmake version bradbell@gorst trash]$ cmake --version cmake version 2.6-patch 4 While doing so I am having trouble with the ADD_CUSTOM_TARGET. To be specifc, after building a custom target, cmake seems to forget it

[CMake] Building either shared or static version of a library on Windows

Hi My exports header file for a C/C++ project has the following definitions: #if defined(WIN32) || defined(WIN64) #ifndef LIB_EXPORT #ifdef lib_EXPORTS #define LIB_EXPORT __declspec(dllexport) #else #define LIB_EXPORT __declspec(dllimport) #endif #endif #endif where

Re: [CMake] Building either shared or static version of a library on Windows

There are lots of different ways to do this. The following is an example of what *I* do. - In my CMakeLists.txt file I have this set(DREAM3DLib_BUILT_AS_DYNAMIC_LIB) IF (BUILD_SHARED_LIBS) set(DREAM3DLib_BUILT_AS_DYNAMIC_LIB 1) IF (WIN32)

Re: [CMake] Building either shared or static version of a library on Windows

Le mardi 15 janvier 2013 à 11:31 -0500, Michael Jackson a écrit : There are lots of different ways to do this. The following is an example of what *I* do. - In my CMakeLists.txt file I have this set(DREAM3DLib_BUILT_AS_DYNAMIC_LIB) IF (BUILD_SHARED_LIBS)

Re: [CMake] Building either shared or static version of a library on Windows

On Jan 15, 2013, at 11:44 AM, Bogdan Cristea wrote: Le mardi 15 janvier 2013 à 11:31 -0500, Michael Jackson a écrit : There are lots of different ways to do this. The following is an example of what *I* do. - In my CMakeLists.txt file I have this set(DREAM3DLib_BUILT_AS_DYNAMIC_LIB)

Re: [CMake] Two toolchains simultaneously within the same project?

Hi. 2012/9/28 David Cole david.c...@kitware.com: Please try with a more recent CMake version. The most recent release is 2.8.9. ExternalProject was first introduced in 2.8.0, and many many issues have been fixed in it over the last 2 years. I am now using CMake 2.8.10.2, and indeed,

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1606-gb97e9ba

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 b97e9ba6a0a5797b70d8225e9111396c25348ef6 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-450-gd870867

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 d870867570f84702f789100a43762e4536721b1a (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-454-g8d91e23

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 8d91e23565e01765d821716fcd3d64d7e45e6440 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-456-ga269e65

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 a269e65de47f2f91b5d2cef8660c6f81f5e743dd (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1627-g1cd6a5d

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 1cd6a5ddc52a56d3aa0722c4afcd6a4f6a14dff5 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-473-g3a7d1ce

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 3a7d1ce3ff0ea0565d463a341f42acd6bed8a6c4 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-1629-g867ae68

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 867ae688ca39a876083f3c5b2880e086208112d6 (commit) via