Thanks for assistance. I forgot 'reply all'. Will be better next time :-)
On 24/09/14 14:58, Petr Kmoch wrote:
> I don't know why @ was inserted, but here's why it overrides the
> absolute path: because it has no special meaning. The path then
> becomes "@/sbin", which is not an absolute path (doe
I don't know why @ was inserted, but here's why it overrides the absolute
path: because it has no special meaning. The path then becomes "@/sbin",
which is not an absolute path (doesn't start with '/'), so the install
prefix is prepended normally. Bear in mind that Unix directory and file
names can
Hi Jeremy.
Does ${BUILD_BIN} perhaps start with a slash? If so, it would be
interpreted as an absolute path, which of course ignores
CMAKE_INSTALL_PREFIX.
Petr
On Wed, Sep 24, 2014 at 7:58 AM, Jeremy Ardley
wrote:
> I am using cmake 2.8.9 on debian wheezy. I'm fairly new to using cmake.
>
> M
I am using cmake 2.8.9 on debian wheezy. I'm fairly new to using cmake.
My CMakelists.txt file starts with
cmake_minimum_required(VERSION 2.6)
SET(CMAKE_INSTALL_PREFIX /home/jeremy/Projects/local/)
project(myproject)
Finishing with
INSTALL ( PROGRAMS ${CMAKE_CURRENT_BINARY_DIR}/@APPLICATI
