Rpath and binary reuse
summary
Claim: embedded runtime library paths cause unpredictable linking and security risk when binaries move. Linux linker prefers executable rpath then LD_LIBRARY_PATH then system config, OS X adds @rpath and @executable_path semantics, Windows relies on PATH. Conan uses tools to edit binaries and offers to remove rpaths so packages are relocatable but binary patching is fragile and current integration is incomplete so the approach sometimes works and sometimes breaks.
AI-written summary · about
related talks
01h 02mC++ Shared Libraries and Where To Find Them
01h 00mLinkers, Loaders and Shared Libraries in Windows, Linux, and C++
37mCross-Building Strategies in the Age of C++ Package Managers
55mDynamically Loaded Libraries Outside the Standard
40mRuby's Environment Variable API
05mClang on Windows: It's a Thing
58mHow Can Package Managers Handle ABI (In)compatibility in C++?
16mMind the Gap (Between Your Code and Your Toolchain)