From 137f03b9a34fb39e5321524ab11fa31276458476 Mon Sep 17 00:00:00 2001
From: Matthias Vogelgesang <matthias.vogelgesang@kit.edu>
Date: Tue, 29 Oct 2013 09:05:51 +0100
Subject: Use ConfigurePaths to get installation paths

The advantage is twofold: 1) we have a clear separation between setting up the
paths and actually using them, 2) the interface is very likely as configure
scripts and makes integration into build system a bit easier.
---
 CMakeLists.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

(limited to 'CMakeLists.txt')

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 25c07e3..6c5ede2 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -66,11 +66,14 @@ macro(create_enums prefix template_prefix header_list)
 endmacro()
 #}}}
 #{{{ Configure
+include(ConfigurePaths)
+configure_paths(UCA)
+
+set(UCA_PLUGINDIR "${UCA_LIBDIR}/uca")
 set(LIB_INSTALL_DIR "lib${LIB_SUFFIX}")
 
 configure_file(${CMAKE_CURRENT_SOURCE_DIR}/package.sh.in
                ${CMAKE_CURRENT_BINARY_DIR}/package.sh)
-
 #}}}
 #{{{ Common dependencies
 find_package(PkgConfig)
-- 
cgit v1.2.3