[cmake-developers] [CMake 0013050]: FindOpenGL not working on Cygwin

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

Re: [cmake-developers] How to handle package Config.cmake files with dependencies ?

On Saturday 17 March 2012, Alexander Neundorf wrote: On Tuesday 13 March 2012, Brad King wrote: On 3/13/2012 4:23 PM, Alexander Neundorf wrote: Then force-push back to the stage for another review. Done. Thanks. I rewrote and force-pushed the topic to make a few changes:

[cmake-developers] [CMake 0013051]: DeployQt4.cmake: INSTALL not scriptable

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

[cmake-developers] [CMake 0013052]: BundleUtilities (fixup_bundle_item): location checks are too strict

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

[cmake-developers] [CMake 0013053]: Command line dialog not visible

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

[CMake] specifying complex test behavior

Hello, Is it possible to specify complex behavior for determining if a test was successful. For example, if we have add_test(Differ executable args) I want to specify that the test named Differ is successful if the output obtained by running the specified executable matches a certain file, i.e

Re: [CMake] specifying complex test behavior

2012/3/18 Ajay Panyala a...@csc.lsu.edu: Hello, Is it possible to specify complex behavior for determining if a test was successful. For example, if we have add_test(Differ executable args) I want to specify that the test named Differ is successful if the output obtained by running the

[Cmake-commits] CMake branch, next, updated. v2.8.7-3192-gf524357

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

[Cmake-commits] CMake branch, next, updated. v2.8.7-3199-ga36e092

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

[Cmake-commits] CMake branch, next, updated. v2.8.7-3201-g4f0ba8e

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

[Cmake-commits] CMake branch, master, updated. v2.8.7-671-g9987d95

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 9987d9522be45a2c63d68298da6696d965693348 (commit) from