Hello,
In the manual the install(FILES...) command is described as this:
install( files... DESTINATION
[PERMISSIONS permissions...]
[CONFIGURATIONS [Debug|Release|...]]
[COMPONENT ]
[RENAME ] [OPTIONAL])
So what is the meaning of COMPONENT and OPTIONAL?
Greetings
Hi Andrey,
On Tue, Feb 17, 2015 at 5:52 PM, Andrey Pokrovskiy
wrote:
>
> I don't see how External_OpenSSL.cmake is used in Slicer (probably
> some weird scheme is involved).
>
We used "Artichoke" that provides a set of convenience function to managed
"superbuild" based project.
See [1] and [2]
I agree with Andrey, there should be a way to use interface library type with
generated headers.
There's a workaround but it involves manual set up of extra dependencies solely
for dependency tracking. You have to add dependency between a target which
consumes the generated headers and a cus
Hi,
Current CMake disallows Interface Libraries to have dependencies.
However, I suspect that was done for a reason. Here is the commit for
that change:
commit 6db7e6d24c68085f16dcf6d8a86ae0f74e9a1f01
Author: Stephen Kelly
Date: Wed Dec 25 15:11:50 2013 +0100
add_dependencies: Disal
Thanks for your reply, Jean-Christophe.
I don't see how External_OpenSSL.cmake is used in Slicer (probably
some weird scheme is involved).
But from what I see, it supposed to be used like that:
include(External_OpenSSL)
add_executable(my_executable main.cpp ...)
target_include_directories(m
Hi,
I would like to include a generated file into a package. I have something like
that:
include(CPack)
add_custom_command (OUTPUT hgHash.txt
COMMAND hg --debug id -i >hgHash.txt
COMMENT "Getting hg hash")
add_custom_target (hg_hash
DEPENDS hgHash.txt
COMMENT "hg_hash target")
Hi Andrey,
Since there is already a FindOpenSSL.cmake module [1], configuring the
consumer project with the variable expected by the FindOpenSSL.cmake module
is the easiest.
See
https://github.com/Slicer/Slicer/blob/ee84fba523d85be3539bf8c83c8eb73d4f59cfff/SuperBuild/External_OpenSSL.cmake#L231-L
Hi,
I'm using ExternalProject_Add() to build OpenSLL library. After
install step I have following artifacts available:
* libcrypto.a
* libssl.a
* include/openssl/*.h
I wonder, what is the "canonical" way to make those artifacts
available for other targets in the project?
FindPackage style thing
On Tuesday, February 17, 2015 10:28:26 Robert Ramey wrote:
> I'm using CMake 3.02 through CMake GUI.
>
> I have a CMake project which I want to build using Eclipse Luna (the most
> recent eclipse). But the GUI doesn't present me with that option. I tried
> to use the latest one (Helios) but it s
I'm using CMake 3.02 through CMake GUI.
I have a CMake project which I want to build using Eclipse Luna (the most
recent eclipse). But the GUI doesn't present me with that option. I tried
to use the latest one (Helios) but it seems that it won't work with this
option.
What should I do in orde
Thanks Nils,
It makes perfect sense with your explanation! Did not know anything about
this RPATH family of variables before.
Cheers and thanks again
On Fri, Feb 13, 2015 at 11:28 AM, Nils Gladitz
wrote:
> On 02/12/2015 06:40 PM, Sergio Vera wrote:
>
>> Dear CMake users,
>>
>> I'm developing a
11 matches
Mail list logo