Severe behavioural change regressions in release branch

Ben Boeckel ben.boeckel-5opLkZggLXlBDgjK7y7TUQ at
Mon Oct 27 21:22:45 GMT 2014

On Tue, Oct 28, 2014 at 09:58:58 +1300, Ben Cooksley wrote:
> If anyone is interested, help would be appreciated to get a Contracts
> style build up and running.
> In particular, pointers to documentation on how to perform such builds
> would be appreciated - we'll need to run "make install" for parts of
> it which doesn't seem to happen in any of the existing examples as far
> as I can see.

Since it's a CMake build, ExternalProject should make it fairly
straightforward. A quick sketch of the non-boilerplate code I see in the
current contracts tests:

      GIT_REPOSITORY [...]
      GIT_TAG        [...] # The oldest supported release.
      DEPENDS        kdelibs
      GIT_REPOSITORY [...]
      GIT_TAG        [...] # The oldest supported release.
        # Might not be necessary.

The rationale for using the oldest supported release is so that we make
sure whatever was written *then* still works today.


Powered by

Please keep messages on-topic and check the CMake FAQ at:

Kitware offers various services to support the CMake community. For more information on each offering, please visit:

CMake Support:
CMake Consulting:
CMake Training Courses:

Visit other Kitware open-source projects at

Follow this link to subscribe/unsubscribe:

More information about the kde-core-devel mailing list