[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: [cmake-developers] Severe behavioural change regressions in release branch
From: Ben Boeckel <ben.boeckel () kitware ! com>
Date: 2014-10-27 21:22:45
Message-ID: 20141027212245.GA9878 () megas ! kitwarein ! com
[Download RAW message or body]
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:
externalproject_add(kdelibs
GIT_REPOSITORY [...]
GIT_TAG [...] # The oldest supported release.
CMAKE_ARGS
[...]
INSTALL_DIR "${CMAKE_CURRENT_BINARY_DIR}/install")
externalproject_add(someotherkdelib
DEPENDS kdelibs
GIT_REPOSITORY [...]
GIT_TAG [...] # The oldest supported release.
CMAKE_ARGS
# Might not be necessary.
"-DCMAKE_MODULE_PATH={$CMAKE_CURRENT_BINARY_DIR}/install/lib/cmake"
[...]
INSTALL_DIR "${CMAKE_CURRENT_BINARY_DIR}/install")
The rationale for using the oldest supported release is so that we make
sure whatever was written *then* still works today.
--Ben
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic