summaryrefslogtreecommitdiff
path: root/plugins/efi_resolver
diff options
context:
space:
mode:
authorMark Rowe <mark@vector35.com>2025-07-29 16:20:49 -0700
committerMark Rowe <mark@vector35.com>2025-08-14 15:43:38 -0700
commit0c572b1343d1e98574b7bc46169947f2dd5a257d (patch)
tree586668986db0ce2e5e73a4977f2efa8b5832b19c /plugins/efi_resolver
parent5957643780031478927457215296267592446286 (diff)
[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.
Diffstat (limited to 'plugins/efi_resolver')
-rw-r--r--plugins/efi_resolver/CMakeLists.txt2
1 files changed, 2 insertions, 0 deletions
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)