rust

Author: altunenes

content/posts/gstmac.md

@@ -0,0 +1,41 @@
++++
+title = "How We Fixed macOS GStreamer Library Path Issues in Rust Releases"
+date = "2025-09-02"
+[taxonomies]
+tags=["GStreamer", "macOS", "Rust"]
++++
+
+## <span style="color:orange;">How We Fixed macOS GStreamer Library Path Issues in Rust Releases</span>
+
+I spent hours debugging why our Rust application worked perfectly in development but failed with GStreamer library conflicts in release builds on macOS. Users would see this error when double-clicking the app:
+
+```bash
+  objc[43583]: Class GstCocoaApplicationDelegate is implemented in both
+  /Library/Frameworks/GStreamer.framework/Versions/1.0/lib/libgstreamer-1.0.0.dylib
+  and /Users/user/app/gstreamer/lib/libgstreamer-1.0.0.dylib
+```
+
+### <span style="color:orange;">The Problem</span>
+
+Our GitHub Actions release script was trying to fix `@rpath` entries using `install_name_tool` to point to bundled libraries, but the commands were silently failing.
+
+### <span style="color:orange;">The Root Cause</span>
+
+Rust binaries don't have enough header padding by default for `install_name_tool` to modify library paths.
+
+### <span style="color:orange;">The Solution</span>
+
+Add this linker flag to your macOS Rust builds:
+
+```bash
+export RUSTFLAGS="$RUSTFLAGS -C link-arg=-Wl,-headerpad_max_install_names"
+```
+
+This reserves enough space in the binary header for dynamic library path modifications.
+
+- **Before:** Binary had unfixable `@rpath` entries → loaded both system and bundled GStreamer → conflicts
+- **After:** Binary library paths properly fixed → loads only bundled GStreamer → works perfectly
+
+### <span style="color:orange;">Key Lesson</span>
+
+Always verify that your `install_name_tool` commands actually succeed. Silent failures can waste hours of debugging!