Collectives™ on Stack Overflow
Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about Collectives
Teams
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
Learn more about Teams
I'm writing a CMakeLists.txt file to build a C++ project of mine, which is composed of
libhybris.so: A shared library with some exported functions.
hybris: An executable which links to libhybris.so
A set of various shared libraries which links to libhybris.so
The problem is that, libhybris.so depends on libpcre (for regular expression capabilities), so I have the following statements:
# libhybris.so generation
add_library( libhybris
SHARED
${LIB_SOURCES} )
# Needed libraries
target_link_libraries( libhybris
pthread
readline )
And one of the shared libraries from point 3, is called pcre.so, so I have the following too:
add_library( pcre SHARED ${PCRE_SOURCES} )
target_link_libraries( pcre
pthread
readline
libhybris )
So, when I run a "cmake .", I have the following error:
-- Configuring done
CMake Error: The inter-target dependency graph contains the following strongly connected component (cycle):
"libhybris" of type SHARED_LIBRARY
depends on "pcre"
"pcre" of type SHARED_LIBRARY
depends on "libhybris"
At least one of these targets is not a STATIC_LIBRARY. Cyclic dependencies are allowed only among static libraries.
Because CMake thinks that the libhybris.so pcre dependency (system libpcre.so) is the same of my pcre.so which it is obviously not.
How can I solve this problem without changing the pcre.so name?
In CMake, the recommended way is to specify any link libraries with the full path. To get the full path for the system library, you can either use FIND_PACKAGE(...)
if supported or simply FIND_LIBRARY(...)
For example,
FIND_LIBRARY( PCRE_SYSTEM_LIB pcre )
ADD_LIBRARY( libhybris SHARED ${LIB_SOURCES} )
TARGET_LINK_LIBRARIES( libhybris
${PCRE_SYSTEM_LIB}
......
This will prevent CMake from expanding something it recognizes as a target (nameley pcre
) to the full path of that target.
–
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.