Human:
I'm excited to use StableApproach on my Mac setup (never used it before) but ran into an issue with the build. The following write-up is generated from a ChatGPT conversation. I've eyeballed it and the issue checks out. Happy to test and help out if I can. This plugin sounds amazing!
Non-Human:
Summary
The StableApproach plugin fails to load in X-Plane 12 on macOS due to a missing dependency. The binary appears to be compiled with a hardcoded path to the X-Plane SDK (lib/xplane_sdk/...), which does not exist on end-user systems.
Environment
- OS: macOS (Apple Silicon) 26.4.1 (25E253)
- X-Plane version: 12.4.2-r2-e8339ac0 (build 124201 Apple Silicon)
- Plugin version: 1.5.0-beta.3
Steps to reproduce
- Install plugin into:
X-Plane 12/Resources/plugins/StableApproach/
- Launch X-Plane
- Check Plugins → Plugin Admin or review
Log.txt
Expected behaviour
Plugin loads successfully and appears in the Plugins menu.
Actual behaviour
Plugin fails to load and does not appear in the Plugins menu.
Relevant Log.txt output
dlerror:dlopen(.../StableApproach.xpl, 0x0006): Library not loaded: lib/xplane_sdk/sdk/Libraries/Mac/XPLM.framework/XPLM
Referenced from: .../StableApproach.xpl
Reason: tried: 'lib/xplane_sdk/sdk/Libraries/Mac/XPLM.framework/XPLM' (no such file)
Additional investigation
Running otool -L StableApproach.xpl shows:
lib/xplane_sdk/sdk/Libraries/Mac/XPLM.framework/XPLM
lib/xplane_sdk/sdk/Libraries/Mac/XPWidgets.framework/XPWidgets
These paths indicate the plugin binary is linked against a local SDK path (lib/xplane_sdk/...) instead of relying on X-Plane’s runtime-provided SDK frameworks.
Analysis
This suggests the plugin was compiled with incorrect linker settings, embedding a developer-local SDK path. On macOS, plugins should not reference a bundled or relative SDK path like this—X-Plane provides the required frameworks at runtime.
Suggested fix
Rebuild the plugin with correct linkage against the X-Plane SDK:
- Ensure no hardcoded
lib/xplane_sdk/... paths are embedded
- Link against the SDK as per official X-Plane plugin build guidelines
Notes
- This issue is reproducible on a clean install
- Not related to permissions, quarantine flags, or plugin folder structure
Human:
I'm excited to use StableApproach on my Mac setup (never used it before) but ran into an issue with the build. The following write-up is generated from a ChatGPT conversation. I've eyeballed it and the issue checks out. Happy to test and help out if I can. This plugin sounds amazing!
Non-Human:
Summary
The StableApproach plugin fails to load in X-Plane 12 on macOS due to a missing dependency. The binary appears to be compiled with a hardcoded path to the X-Plane SDK (
lib/xplane_sdk/...), which does not exist on end-user systems.Environment
Steps to reproduce
Log.txtExpected behaviour
Plugin loads successfully and appears in the Plugins menu.
Actual behaviour
Plugin fails to load and does not appear in the Plugins menu.
Relevant Log.txt output
Additional investigation
Running
otool -L StableApproach.xplshows:These paths indicate the plugin binary is linked against a local SDK path (
lib/xplane_sdk/...) instead of relying on X-Plane’s runtime-provided SDK frameworks.Analysis
This suggests the plugin was compiled with incorrect linker settings, embedding a developer-local SDK path. On macOS, plugins should not reference a bundled or relative SDK path like this—X-Plane provides the required frameworks at runtime.
Suggested fix
Rebuild the plugin with correct linkage against the X-Plane SDK:
lib/xplane_sdk/...paths are embeddedNotes