================
@@ -170,11 +170,12 @@ if(ENABLE_SHARED)
# implicitly be exported from libclang.
target_compile_definitions(libclang PRIVATE CLANG_BUILD_STATIC)
elseif(APPLE)
- set(LIBCLANG_LINK_FLAGS " -Wl,-compatibility_version -Wl,1")
- set(LIBCLANG_LINK_FLAGS "${LIBCLANG_LINK_FLAGS} -Wl,-current_version
-Wl,${LLVM_VERSION_MAJOR}.${LLVM_VERSION_MINOR}.${LLVM_VERSION_PATCH}")
-
- set_property(TARGET libclang APPEND_STRING PROPERTY
- LINK_FLAGS ${LIBCLANG_LINK_FLAGS})
+ if(LLVM_VERSIONED_DYLIB_NAME_ON_DARWIN)
----------------
tamird wrote:
> It is a requirement on macOS and in our toolchain that we have to link across
> major version boundaries.
Can you help me understand why this is a requirement *specifically on macOS*?
In particular, what behavior or distribution model depends on
`libclang`/`libLTO` keeping an unversioned dylib identity *on macOS only*?
https://github.com/llvm/llvm-project/pull/189004
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
