Product Name / Compiler Output filename

[Ben Russell]

Ran into a nice quirk of Dynamic Library programming today.

I had Gizmo's project set to automatically output to a file called "mac.xpl"

I had a second plugin project, also set to automatically output to a file called "mac.xpl"

These filenames were setup using Xcodes "product name" fields in the build config.

When X-Plane would load the 2nd plugin project, the Operating System would re-load Gizmo!

Reason: The dylib is stamped with an internal name... the OS reads it, and for some insane reason, thinks they're the same binary.

(Gizmo is about 4.5 meg, the 2nd project file was only 54kb...)

Conclusion: Renaming your file from "Gizmo_mac.xpl" -> "mac.xpl" and THEN moving it into the X-Plane folders is a LOT safer and plays better with other dylibs.

File under "G" for Glad I never have to think about this cause I use Gizmo scripting instead.