Re: [cmake-developers] Summer of code and Pascal

2013/2/12 Vittorio Giovara vittorio.giov...@gmail.com: Good to hear a positive response! Regarding your questions: What is the state of pascal compilers these days? Are they cross platform? Well GnuPascal is pretty much unsupported nowadays, although some binary distributions still exists,

Re: [cmake-developers] Setting includes, defines and other usage requirements with one command

Brad King wrote: Please try to track down and remove any extra pieces like $LINKED and package_NO_INTERFACES that we added in an attempt to deal with the previous approach's problems. Done now in the linked-usage-cleanup branch. Thanks, Steve. -- Powered by www.kitware.com Visit other

Re: [cmake-developers] Setting includes, defines and other usage requirements with one command

On 02/12/2013 07:20 AM, Stephen Kelly wrote: Brad King wrote: Please try to track down and remove any extra pieces like $LINKED and package_NO_INTERFACES that we added in an attempt to deal with the previous approach's problems. Done now in the linked-usage-cleanup branch. Wonderful,

[cmake-developers] [CMake 0013905]: TO_CMAKE_PATH doens't remove the first ':'

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

Re: [cmake-developers] Adding automatic checks for required targets in target-export files ?

On Monday 11 February 2013, Alexander Neundorf wrote: On Monday 11 February 2013, Brad King wrote: On 02/10/2013 10:14 AM, Alexander Neundorf wrote: 1) either put a check for the required targets in the generated targets file, and make find_package() fail by setting foo_FOUND to FALSE.

Re: [cmake-developers] Depends information in buildsystem files

Brad King wrote: Should we create LINK_LIBRARIES now instead, use it in the macros by directly passing CMAKE_REQUIRED_LIBRARIES to it, and implement the ignoring of -DLINK_LIBRARIES in that case? Yes, we can create LINK_LIBRARIES now for the single-source signature and do nothing yet for

Re: [cmake-developers] Setting includes, defines and other usage requirements with one command

Stephen Kelly wrote: * Can the INCLUDE_DIRETORIES and COMPILE_DEFINITIONS property avoid $LINKED:foo references if foo is linked more than once? Skip appending it if the same reference already exists earlier. In the BEFORE case, prepend it and remove later instances. Yes I'm sure that can

[cmake-developers] [CMake 0013909]: Build fails with exec(): 0509-036 Cannot load program ../bin/ctest

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13909 == Reported By:Ben Lentz Assigned To:

Re: [cmake-developers] Adding automatic checks for required targets in target-export files ?

On Tuesday 12 February 2013, Brad King wrote: On 02/12/2013 01:47 PM, Alexander Neundorf wrote: ... 1) fail immediately in the targets file if a referenced target does not exist yet. If imported targets would be new, I would do this. But since they already exist for some time, there are

[CMake] Fortran_MODULE_DIRECTORY ignored in second subdir

Hi all. I have a problem with Fortran_MODULE_DIRECTORY only being applied in the first of several subdirectory projects. Here's a simplified setup to demonstrate the issue. It has a toplevel C++ project and two subdirectory projects which use Fortran: $cat source_dir/CMakeLists.txt:

Re: [CMake] Fortran_MODULE_DIRECTORY ignored in second subdir

I forgot to add that if, immediately after running CMake, I run it again (without changing a single file), the flags -module foobar appear in the sub2/.../flags.cmake as well. Petr On Tue, Feb 12, 2013 at 2:15 PM, Petr Kmoch petr.km...@gmail.com wrote: Hi all. I have a problem with

Re: [CMake] Fortran_MODULE_DIRECTORY ignored in second subdir

On 02/12/2013 08:15 AM, Petr Kmoch wrote: project(Top) # No Fortran here [snip] My real setup doesn't really allow me to enable Fortran in the toplevel project; is there a way to make this work without that? CMake simply doesn't support this case right now. The language initialization stores

Re: [CMake] Fortran_MODULE_DIRECTORY ignored in second subdir

Thanks very much for clearing this up. I fully understand my setup is a little unorthodox. I'm glad I can now concentrate on finding a workaround instead of wondering what I'm doing wrong. On Tue, Feb 12, 2013 at 3:06 PM, Brad King brad.k...@kitware.com wrote: On 02/12/2013 08:15 AM, Petr

[CMake] MSVC11 not set properly?

Hi, I'm using cmake 2.8.10.2 on Windows 7. For some reason, when I select Visual Studio 11 as the generator (I use Visual Studio Express 2012), the MSVC11 variable is not set, instead MSVC10 is set. This breaks all kinds of stuff, such as FindBoost.cmake (first I thought it's a bug in FindBoost,

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2097-g3bb2ea0

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

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2099-gf4ccda6

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

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2107-g1537ebe

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

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2109-ga5fc93d

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

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2111-gb1caac7

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

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-661-g17a6d3c

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

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-664-gc6c9838

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

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-666-gf0c4d37

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

[Cmake-commits] CMake branch, next, updated. v2.8.10.2-2116-gb79cb53

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

[Cmake-commits] CMake branch, master, updated. v2.8.10.2-667-g1324500

Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index fa1354c..02257a6 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -2,5 +2,5 @@ set(CMake_VERSION_MAJOR 2) set(CMake_VERSION_MINOR 8) set(CMake_VERSION_PATCH 10) -set(CMake_VERSION_TWEAK 20130212