[cmake-developers] [CMake 0012608]: Unexpected %config file declaration.

2011-12-06 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12608 == Reported By:Daniel Morlock Assigned To:

[cmake-developers] [CMake 0012609]: Report when CTEST_COVERAGE_COMMAND is not set

2011-12-06 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://cmake.org/Bug/view.php?id=12609 == Reported By:Mathieu Malaterre Assigned To:

Re: [cmake-developers] Fwd: How to handle different cmake versions in extra-cmake-modules ?

2011-12-06 Thread Brad King
On 12/6/2011 1:13 PM, Alexander Neundorf wrote: Does that look like it should cover all use cases, for peopling wanting to selectively use some things from e-c-m, and fearing that something would break if they simply would make everything available ? That proposal looks good to me. As an

Re: [cmake-developers] Fwd: How to handle different cmake versions in extra-cmake-modules ?

2011-12-06 Thread Alexander Neundorf
On Tuesday 06 December 2011, Brad King wrote: On 12/6/2011 1:13 PM, Alexander Neundorf wrote: Does that look like it should cover all use cases, for peopling wanting to selectively use some things from e-c-m, and fearing that something would break if they simply would make everything

Re: [cmake-developers] Fwd: How to handle different cmake versions in extra-cmake-modules ?

2011-12-06 Thread Brad King
On 12/6/2011 1:37 PM, Alexander Neundorf wrote: On Tuesday 06 December 2011, Brad King wrote: That proposal looks good to me. As an additional suggestion, I think you should always use an ECM version number so people get used to writing it. That way projects can ensure they get a compatible

[cmake-developers] [CMake 0012610]: Uncaught exception in automoc logic on a specific CMakeLists.txt

2011-12-06 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12610 == Reported By:Georg Rudoy Assigned To:

[cmake-developers] [CMake 0012611]: Missing CMAKE_INCLUDE_DIRECTORIES_BEFORE from documentation

2011-12-06 Thread Mantis Bug Tracker
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=12611 == Reported By:Fraser Hutchison Assigned To:

[CMake] import/export and DLL's

2011-12-06 Thread Totte Karlsson
Hi, I have a project where several DLL's are to be built, say A, B and C. B needs to import functions/classes from A, and C need to import functions from both A and B. In each library, a flag is defined for exporting or importing, i.e. __declspec(dllexport) or __declspec(import) The build

Re: [CMake] Copy a input file from src folder to EXECUTABLE_OUTPUT_PATH

2011-12-06 Thread Totte Karlsson
I want to be moved to the same folder as the executables. How do I do that in CMake? At configuration time: CONFIGURE_FILE(path/to/input.txt ${EXECUTABLE_OUTPUT_PATH} COPYONLY) Note that the destination directory, i.e. the EXECUTABLE_OUTPUT_PATH, possibly must already exist, and refer to

Re: [CMake] import/export and DLL's

2011-12-06 Thread Michael Wild
On 12/06/2011 09:47 AM, Totte Karlsson wrote: Hi, I have a project where several DLL's are to be built, say A, B and C. B needs to import functions/classes from A, and C need to import functions from both A and B. In each library, a flag is defined for exporting or importing, i.e.

Re: [CMake] import/export and DLL's

2011-12-06 Thread Totte Karlsson
Thanks for feedback You misunderstand and misuse the DEFINE_SYMBOL property. All the IMPORT_X_DLL symbols are wrong, you have to remove them. But when building the B, and C dll the import symbols need to be defined somehow. See my export/import header below. CMake will only add the

[CMake] make install files

2011-12-06 Thread H Xu
Hello, In cmake, install command is used to indicate the files that need to be installed, and install(DIRECTORY ...) could be used to install directories. However, I can't find a way to install files in a directory EXCEPT a few files that I do not want to install. Is it possible to do this?

Re: [CMake] make install files

2011-12-06 Thread Eric Noulard
2011/12/6 H Xu xusu...@gmail.com: Hello, In cmake, install command is used to indicate the files that need to be installed, and install(DIRECTORY ...) could be used to install directories. However, I can't find a way to install files in a directory EXCEPT a few files that I do not want to

Re: [CMake] import/export and DLL's

2011-12-06 Thread Michael Wild
On 12/06/2011 10:42 AM, Totte Karlsson wrote: Thanks for feedback You misunderstand and misuse the DEFINE_SYMBOL property. All the IMPORT_X_DLL symbols are wrong, you have to remove them. But when building the B, and C dll the import symbols need to be defined somehow. See my export/import

Re: [CMake] Best practices/preferred methods for linking external libraries

2011-12-06 Thread Matthew LeRoy
On Dec 5, 2011, at 5:57 PM, Michael Jackson wrote: On Dec 5, 2011, at 5:36 PM, Matthew LeRoy wrote: On Dec 4, 2011, at 11:59 AM, Michael Jackson wrote: On Dec 1, 2011, at 4:56 PM, Matthew LeRoy wrote: We began using CMake a few months ago for a couple of small cross- platform

Re: [CMake] Best practices/preferred methods for linking external libraries

2011-12-06 Thread Michael Jackson
On Dec 6, 2011, at 9:56 AM, Matthew LeRoy wrote: On Dec 5, 2011, at 5:57 PM, Michael Jackson wrote: On Dec 5, 2011, at 5:36 PM, Matthew LeRoy wrote: On Dec 4, 2011, at 11:59 AM, Michael Jackson wrote: On Dec 1, 2011, at 4:56 PM, Matthew LeRoy wrote: We began using CMake a few

Re: [CMake] import/export and DLL's

2011-12-06 Thread Michael Jackson
Read this article. http://www.cmake.org/Wiki/BuildingWinDLL If you have questions after that please post. That article should clear everything up. Thanks ___ Mike JacksonPrincipal Software Engineer BlueQuartz

[CMake] hear hear

2011-12-06 Thread Daniel Dekkers
On Dec 4, 2011, at 11:59 AM, Michael Jackson wrote: I think if the CMake community took a vote we could probably come up with an Exemplar Find*.cmake file that is good for someone trying to develop a new one. Yes please. And I think in general that is true. Of course it is more interesting

Re: [CMake] Best practices/preferred methods for linking external libraries

2011-12-06 Thread Matthew LeRoy
On 2011-12-03 14:54-0800 Alan W. Irwin wrote: On 2011-12-03 12:42-0800 Alan W. Irwin wrote: On 2011-12-02 19:33- Matthew LeRoy wrote: Assuming we want to just put the install tree in version control somewhere, and have ProjectB's list files reference the install tree out of

Re: [CMake] hear hear

2011-12-06 Thread Mateusz Łoskot
On 6 December 2011 16:27, Daniel Dekkers d.dekk...@cthrough.nl wrote: On Dec 4, 2011, at 11:59 AM, Michael Jackson wrote: I think if the CMake community took a vote we could probably come up with an Exemplar Find*.cmake file that is good for someone trying to develop a new one. Yes please.

Re: [CMake] hear hear

2011-12-06 Thread Alexander Neundorf
On Tuesday 06 December 2011, Mateusz Łoskot wrote: On 6 December 2011 16:27, Daniel Dekkers d.dekk...@cthrough.nl wrote: On Dec 4, 2011, at 11:59 AM, Michael Jackson wrote: I think if the CMake community took a vote we could probably come up with an Exemplar Find*.cmake file that is good

Re: [CMake] Best practices/preferred methods for linking external libraries

2011-12-06 Thread David Cole
On Tue, Dec 6, 2011 at 12:08 PM, Matthew LeRoy mle...@minitab.com wrote: On 2011-12-03 14:54-0800 Alan W. Irwin wrote: On 2011-12-03 12:42-0800 Alan W. Irwin wrote: On 2011-12-02 19:33- Matthew LeRoy wrote: Assuming we want to just put the install tree in version control somewhere,

[CMake] New type of cache variable: lists

2011-12-06 Thread Robert Dailey
Has anyone thought of creating a LIST type for cache variables? In CMake GUI on Windows, this would be represented by a combo-box or drop-down box that allows the user to pick one item out of a list of available items. Is this possible? - Robert Dailey -- Powered by www.kitware.com

Re: [CMake] New type of cache variable: lists

2011-12-06 Thread David Doria
On Tue, Dec 6, 2011 at 4:19 PM, Robert Dailey rcdai...@gmail.com wrote: Has anyone thought of creating a LIST type for cache variables? In CMake GUI on Windows, this would be represented by a combo-box or drop-down box that allows the user to pick one item out of a list of available items. Is

Re: [CMake] New type of cache variable: lists

2011-12-06 Thread David Cole
On Tue, Dec 6, 2011 at 4:26 PM, David Doria daviddo...@gmail.com wrote: On Tue, Dec 6, 2011 at 4:19 PM, Robert Dailey rcdai...@gmail.com wrote: Has anyone thought of creating a LIST type for cache variables? In CMake GUI on Windows, this would be represented by a combo-box or drop-down box

Re: [CMake] New type of cache variable: lists

2011-12-06 Thread Robert Dailey
Thanks for that info David. I have to say that the way this is setup feels kind of duct-taped together. I expected the documentation for such a feature to be under 'set' in the docs, but it wasn't. Plus the option in the list that is the default must be specified in 2 different locations. I think

[CMake] Question about add_custom_target

2011-12-06 Thread Robert Dailey
Does $CONFIGURATION work in add_custom_target as it does in add_custom_command? The documentation doesn't state anything about this that I can see, but it seems like it should work. - Robert Dailey -- Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [CMake] New type of cache variable: lists

2011-12-06 Thread David Cole
On Tue, Dec 6, 2011 at 5:13 PM, Robert Dailey rcdai...@gmail.com wrote: Thanks for that info David. You're welcome. I have to say that the way this is setup feels kind of duct-taped together. It is kind of duct-taped together. (It was better than using WD-40...) I expected the

Re: [CMake] import/export and DLL's

2011-12-06 Thread Totte Karlsson
Well, then just use add_definitions(-DIMPORT_X_DLL). If -DEXPORT_X_DLL is present, it will override your export/import header definitions for the import case, and everything should be fine. Not sure what you mean by override. If both symbols are defined, MTK_COMMON will be defined as

Re: [CMake] import/export and DLL's

2011-12-06 Thread Totte Karlsson
On 12/6/2011 8:10 AM, Michael Jackson wrote: Read this article. http://www.cmake.org/Wiki/BuildingWinDLL Yeah, I did start with that one. My main problem was (as M. Wild) pointed out, defining the build flags correctly. I ended up using add_definitions(-DEXPORT_MOLECULE_DLL) In the article,

Re: [CMake] make install files

2011-12-06 Thread H Xu
On 2011/12/6 20:43, Eric Noulard wrote: 2011/12/6 H Xuxusu...@gmail.com: Hello, In cmake, install command is used to indicate the files that need to be installed, and install(DIRECTORY ...) could be used to install directories. However, I can't find a way to install files in a directory EXCEPT

Re: [CMake] import/export and DLL's

2011-12-06 Thread Michael Wild
On 12/07/2011 01:49 AM, Totte Karlsson wrote: Well, then just use add_definitions(-DIMPORT_X_DLL). If -DEXPORT_X_DLL is present, it will override your export/import header definitions for the import case, and everything should be fine. Not sure what you mean by override. If both symbols

[Cmake-commits] CMake branch, next, updated. v2.8.6-2143-g9cbb99c

2011-12-06 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 9cbb99c110721b492d852c6a2510ce28a069e862 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.6-2145-ge23013e

2011-12-06 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 e23013e4a96908d92a33041da93bf629d1dee0dc (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.6-309-g01e8253

2011-12-06 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, master has been updated via 01e825332ccb5773c716b18687c2862addca0db5 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.6-311-g03aeccd

2011-12-06 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, master has been updated via 03aeccd4ae9db9388107794678088cded9e4ad4d (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.6-315-g4c84aa7

2011-12-06 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, master has been updated via 4c84aa7346821958834fb0de5e0862d8d5718cd9 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.6-317-gcc35c8f

2011-12-06 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, master has been updated via cc35c8fad3e72365336770d4fda579254d121137 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.6-321-gb8c0dd4

2011-12-06 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, master has been updated via b8c0dd48b045457b97386ed6bad5f31b5788c6c5 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.6-329-g35017df

2011-12-06 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, master has been updated via 35017df53ccd66fd6b73cdc2608ede5dfadfa4bb (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.6-331-gde9dc82

2011-12-06 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, master has been updated via de9dc82779346bef6dc05916b90d5d6af661dab8 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.6-333-g9f18f64

2011-12-06 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, master has been updated via 9f18f64c7cfe57df96b6c2cd19d383f9532b6827 (commit) via

[Cmake-commits] CMake branch, next, updated. v2.8.6-2157-ga286108

2011-12-06 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 a286108643fc5768f825060fc25c6cbc47fb7f66 (commit) via

[Cmake-commits] CMake branch, master, updated. v2.8.6-334-g6fb2a38

2011-12-06 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 6fb2a38b0a672959a7ecc8fe4d07350371486310 (commit) from