> Yes but you may still want to separate BUILD from SOURCE tree
> and install in
>
> ${PROJECT_BINARY_DIR}/bin
Thanks, I'll consider this option too. I can't use it at the moment
though since users of the app got used to the "bin" directory in the
top level of the source tree...
> That's right, i
2009/2/17 Pavel Shevaev :
>> If your binary to install is a CMake target (like in your example)
>> you should use:
>>
>> install(targets foo
>>RUNTIME DESTINATION ${foo_SOURCE_DIR}/bin)
>>
>
> This one didn't work neither :(
>
>> moreover installing in ${foo_SOURCE_DIR} is a bit strang
> If your binary to install is a CMake target (like in your example)
> you should use:
>
> install(targets foo
>RUNTIME DESTINATION ${foo_SOURCE_DIR}/bin)
>
This one didn't work neither :(
> moreover installing in ${foo_SOURCE_DIR} is a bit strange,
Well, there is a reason for this.
2009/2/17 Pavel Shevaev :
> Folks, what can be the reason for install target not to be called? I
> have something like this in my CMakeLists.txt:
>
> add_executable(foo src1 src2 src3)
> target_link_libraries(foo ${libs})
> install(PROGRAMS ${foo_BINARY_DIR}/foo
> DESTINATION ${foo_SOU
Folks, what can be the reason for install target not to be called? I
have something like this in my CMakeLists.txt:
add_executable(foo src1 src2 src3)
target_link_libraries(foo ${libs})
install(PROGRAMS ${foo_BINARY_DIR}/foo
DESTINATION ${foo_SOURCE_DIR}/bin
)
And for s
