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' swithe
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
On Fri, Oct 14, 2011 at 11:22 AM, Hendrik Sattler
wrote:
>
> 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)
> Copy the headers i
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
project
On 10/13/2011 10:56 PM, Robert Dailey wrote:
> On Thu, Oct 13, 2011 at 3:47 PM, Michael Hertling wrote:
>
>> 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_PR
On Thu, Oct 13, 2011 at 3:47 PM, Michael Hertling wrote:
> 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 ${CMAKE_BIN
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, Rob
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
> ne
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 insta
2009/3/10 Sharon Melamed
> 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 directorie
2009/3/10 Sharon Melamed
> 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 B
-- Forwarded message --
From: ankit jain
Date: 2009/3/10
Subject: Re: [CMake] install question
To: Sharon Melamed
2009/3/10 Sharon Melamed
>Hi,
>
>
>
> My main CmakeList.txt file look like this:
>
>
>
> cmake_minimum_required (VE
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)
add_subdi
13 matches
Mail list logo
