<div dir="ltr">Hi,<div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 3:50 PM, Mojca Miklavec <span dir="ltr"><<a href="mailto:mojca.miklavec.lists@gmail.com" target="_blank">mojca.miklavec.lists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear list members,<br>
<br>
I often like or need to install two versions of the same software.<br>
Ideally the software should put its files by default to<br>
$prefix/include/$NAME/*.h<br>
$prefix/lib/$NAME/*.dylib<br>
...<br>
($prefix => $CMAKE_INSTALL_PREFIX)<br>
<br>
and in order to be able to install multiple versions side-by-side I<br>
would like to be able to specify something like<br>
-DCMAKE_INSTALL_INCLUDEDIR=include/$NAME/$VERSION<br>
-DCMAKE_INSTALL_LIBDIR=lib/$NAME/$VERSION<br>
to end up with<br>
$prefix/include/$NAME/$VERSION/*.h<br>
$prefix/lib/$NAME/$VERSION/*.dylib<br>
instead of default paths.<br></blockquote><div><br></div><div>Do you have any reasons that speak against using separate prefixes for each version of that software? In particular since such a setup will make your life harder when you want to use the installed software in some cmake-based project. In that case you'd have to manually specify include-dir and lib-dir when configuring the project since many find-modules simply expect a 'standard' unix-like layout below the prefix under which they should search for a given software. So they don't look into include/<version> or lib/<version> so you'd need to specify that manually. Compared with the ease of just specifying CMAKE_PREFIX_PATH to the installation directory for the version you want thats a lot more effort each time you setup a build directory.</div>
<div><br></div><div>Andreas </div><div><br></div></div></div></div>