[CMake] a cmake install question

Greetings, A cmake install question:- When installing say an unknown package (one where only installation prefix is described) appart from such $CMAKE_INSTALL_DIRECTORY (or prefix), are there 'generic' swithes to fix other directories such as --sysconfdir (normally /etc) --mandir

Re: [CMake] a cmake install question

On Monday 28 May 2012, luxInteg wrote: Greetings, A cmake install question:- When installing say an unknown package (one where only installation prefix is described) appart from such $CMAKE_INSTALL_DIRECTORY (or prefix), are there 'generic' swithes to fix other directories

Re: [CMake] install() question

On Thu, 13 Oct 2011 12:09:41 -0500, Robert Dailey wrote: First of all I'm using cmake 2.8.6 and generating Visual Studio 2003 projects with it. There is a particular project that needs to first copy its header files to a specific directory in a specific structure. After that, all other

Re: [CMake] install() question

On Fri, Oct 14, 2011 at 11:22 AM, Hendrik Sattler p...@hendrik-sattler.dewrote: Yes. Compilation of a project should always be possible without polluting the system. For other programs or libraries in the same source tree, install() is not the right thing. You have several options: a)

[CMake] install() question

First of all I'm using cmake 2.8.6 and generating Visual Studio 2003 projects with it. There is a particular project that needs to first copy its header files to a specific directory in a specific structure. After that, all other projects need to reference this project's source code from the

Re: [CMake] install() question

On 10/13/2011 07:09 PM, Robert Dailey wrote: First of all I'm using cmake 2.8.6 and generating Visual Studio 2003 projects with it. There is a particular project that needs to first copy its header files to a specific directory in a specific structure. After that, all other projects need to

Re: [CMake] install() question

I used EXECUTE_PROCESS(COMMAND cmake -E copy_if_different ${SOURCE} ${CMAKE_BINARY_DIR}/${BASENAME}.cpp ) which is done when cmake is run (before vs builds) only problem with this is that to update that souce you need to always run cmake before build On Thu, Oct 13, 2011 at 10:09 AM,

Re: [CMake] install() question

On Thu, Oct 13, 2011 at 3:47 PM, Michael Hertling mhertl...@online.dewrote: You might use an installation component for the concerned headers: CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR) PROJECT(INSTCOMP C) SET(CMAKE_VERBOSE_MAKEFILE ON) SET(F_PREFIX /dev/shm CACHE PATH ) FILE(WRITE

Re: [CMake] install() question

On 10/13/2011 10:56 PM, Robert Dailey wrote: On Thu, Oct 13, 2011 at 3:47 PM, Michael Hertling mhertl...@online.dewrote: You might use an installation component for the concerned headers: CMAKE_MINIMUM_REQUIRED(VERSION 2.8 FATAL_ERROR) PROJECT(INSTCOMP C) SET(CMAKE_VERBOSE_MAKEFILE ON)

Re: [CMake] install question

2009/3/10 Sharon Melamed shar...@voltaire.com Hi, My main CmakeList.txt file look like this: cmake_minimum_required (VERSION 2.6) project (vos) Same thing happens to me also. The problem is of RPATH settings. the path your cmakelist links to while installing is not set for the sub

[CMake] install question

Hi, My main CmakeList.txt file look like this: cmake_minimum_required (VERSION 2.6) project (vos) add_subdirectory (system BUILD) add_subdirectory (osal BUILD) add_subdirectory (logger BUILD) add_subdirectory (loggerConfigTool BUILD) add_subdirectory (voltSyslogd BUILD)

[CMake] install question

-- Forwarded message -- From: ankit jain ankitgu...@gmail.com Date: 2009/3/10 Subject: Re: [CMake] install question To: Sharon Melamed shar...@voltaire.com 2009/3/10 Sharon Melamed shar...@voltaire.com Hi, My main CmakeList.txt file look like

Re: [CMake] install question

2009/3/10 Sharon Melamed shar...@voltaire.com Hi, My main CmakeList.txt file look like this: cmake_minimum_required (VERSION 2.6) project (vos) add_subdirectory (system BUILD) add_subdirectory (osal BUILD) add_subdirectory (logger BUILD) add_subdirectory (loggerConfigTool