An alternate solution is to use generator expression TARGET_LINKER_FILE_NAME
because the linker is also able to use full path names rather than radical
names as library input.
Le 22 juil. 2019 à 17:55 +0200, Dustyn Blasig , a écrit :
> Thanks, Marc. That is exactly what I need, but I'm stuck with
Thanks, Marc. That is exactly what I need, but I'm stuck with 3.12.4 for
the foreseeable future. Is there a way to get the equivalent behavior in
older versions?
On Mon, Jul 22, 2019 at 1:04 AM Marc CHEVRIER
wrote:
> You can use generator expression TARGET_FILE_BASE_NAME, available with
> versio
You can use generator expression TARGET_FILE_BASE_NAME, available with version
3.15.
Le 22 juil. 2019 à 05:24 +0200, Dustyn Blasig , a écrit :
> Hi All,
>
> I am integrating a legacy Makefile with our CMake flow, and need to pass the
> name of a CMake library target to the Makefile via add_custom
Hi All,
I am integrating a legacy Makefile with our CMake flow, and need to pass
the name of a CMake library target to the Makefile via
add_custom_command(). The library uses the OUTPUT_NAME property to override
the default.
add_library(foo_lib SHARED ...)
set_target_properties(foo_lib PROPERTIES
