Hi,
I am struggling with the current situation: An executable targets depends on external prebuilt DCMTK static libraries . These static DCMTK libraries have been built against crypto and openssl shared libraries, and the link phase expects to find ssl and crypto shared libraries in the directory where they have been built.
So with this following instruction
target_link_libraries(myapp PRIVATE ${DCMTK_LIBRARIES})
leads to a link command containing
-Lsomeolddirectory/make/build/openssl_1_1_1l/lib
dcmtk/lib/libdcmtls.a
dcmtk/lib/libdcmsr.a
dcmtk/lib/libdcmimage.a
dcmtk/lib/libdcmdsig.a
-lssl
-lcrypto
-ldl
dcmtk/lib/libdcmqrdb.a
dcmtk/lib/libdcmnet.a
dcmtk/lib/libdcmimgle.a
dcmtk/lib/libdcmfg.a
dcmtk/lib/libdcmiod.a
dcmtk/lib/libdcmdata.a
dcmtk/lib/liboflog.a
dcmtk/lib/libofstd.a
DCMTK_LIBRARIES
doesn’t contain ssl or crypto but the static libraries do contain the path someolddirectory/make/build/openssl_1_1_1l/lib
.
Is there any way to prevent target_link_libraries
to populate prebuilt static libraries dependencies?
Or is there a way to remove hardcoded library references from static libraries?
Thank you,
David