From 0c572b1343d1e98574b7bc46169947f2dd5a257d Mon Sep 17 00:00:00 2001 From: Mark Rowe Date: Tue, 29 Jul 2025 16:20:49 -0700 Subject: [Mac] Consistently specify rpaths for plug-ins C++ plug-ins now consistently use the `plugin_rpath` or `ui_plugin_rpath` macros to ensure they have `SKIP_BUILD_RPATH` set when building on Mac (i.e., no `LC_RPATH` is added). Rust plug-ins have their build.rs updated to only specify `-Wl,-rpath` when building for Linux. It is not needed on macOS. On macOS we instead explicitly specify an `@rpath`-relative install name. This doesn't change any behavior, but avoids leaving an absolute path as the library's install name and is consistent with CMake's behavior for C++ plug-ins. --- plugins/efi_resolver/CMakeLists.txt | 2 ++ 1 file changed, 2 insertions(+) (limited to 'plugins/efi_resolver') diff --git a/plugins/efi_resolver/CMakeLists.txt b/plugins/efi_resolver/CMakeLists.txt index 90f30960..684cae6e 100644 --- a/plugins/efi_resolver/CMakeLists.txt +++ b/plugins/efi_resolver/CMakeLists.txt @@ -25,6 +25,8 @@ file( add_library(efi_resolver SHARED ${SOURCE_FILES}) target_link_libraries(efi_resolver binaryninjaapi) + +plugin_rpath(efi_resolver) target_include_directories(${PROJECT_NAME} PRIVATE "${CMAKE_CURRENT_SOURCE_DIR}/include") target_compile_features(efi_resolver PRIVATE cxx_std_20 c_std_99) -- cgit v1.3.1