what to do about plugin linkage collisions in FCPX
what to do about plugin linkage collisions in FCPX
- Subject: what to do about plugin linkage collisions in FCPX
- From: Paul Miller <email@hidden>
- Date: Sun, 26 Aug 2012 09:14:31 -0500
I have a plugin that links statically with a third party library. When
it is used while another third-party (hi Jim!) plugin (that happens to
link DYNAMICALLY with a different version of the *same* library) is
present in the Plugins folder, FCPX crashes.
The crash stack trace follows my code down into my static copy of the
third-party library, then it jumps into the dynamic version of the
library that is present in the other plugin (which is not applied to the
clip, it's just present in the plugin folder).
This all happens because of the extremely lazy binding going on by
default in Objective C programs. I would expect it to call into my
*statically linked* version of the code, but it ends up in what I
suspect is the first code it encounters with the same function
signature, which in this case is in someone else' (incompatible) library.
Is there any way to work around with XCode linker options to more
permanently bind the function addresses of my code? And although I like
having verbose stack traces, I wouldn't mind turning off the option that
exposes all of my function names. I'm sure users do not want to see
functions such as "WellBleepMeWithaBagOfDildos()" in their crash reports.
Thanks!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden