I found cargo_link_libraries behavior, which according docs is essentially the equivalent to target_link_libraries(), to behave somewhat contrary to expectation.
cargo_link_libraries really just adds -l <lib> and -L <libdir> whereas from target_link_libraries I can at least expect that transitive dependencies are considered (our Rust library might link some FFI).
Additionally, target_link_libraries also supports linking by full path and if a non-target is passed, it is assumed that it is a system library -l <non-target-lib>.
Should not the same be offered by cargo_link_libraries?
I found
cargo_link_libraries
behavior, which according docs isessentially the equivalent to target_link_libraries()
, to behave somewhat contrary to expectation.cargo_link_libraries
really just adds-l <lib>
and-L <libdir>
whereas fromtarget_link_libraries
I can at least expect that transitive dependencies are considered (our Rust library might link some FFI).Additionally,
target_link_libraries
also supports linking by full path and if a non-target is passed, it is assumed that it is a system library-l <non-target-lib>
.Should not the same be offered by
cargo_link_libraries
?