Re: C++ name collisions between plugins
Re: C++ name collisions between plugins
- Subject: Re: C++ name collisions between plugins
- From: Paul Miller <email@hidden>
- Date: Mon, 26 Aug 2013 15:34:36 -0500
- Organization: FXTECH
Yuck. I already have visibility override #pragmas around the Objective
C functions I want exposed. It would be a lot easier to just have
"hide EVERYTHING *except* these 5 things).
I completely agree, but I was happy there was at least a workaround. Currently our list is about 400 entries long, and it's a pain to maintain. In this case nm is your friend (though it still requires hand editing).
I wanted to mention what I think I got to work (at least it seems to be
working).
I ran "nm" to get the names of my FxPlug filter entry points:
[FilterClass1 initWithAPIManager:]
[FilterClass2 initWithAPIManager:]
[FilterClass3 initWithAPIManager:]
I put those lines into a symbols.txt file, then pointed the Linker
option "Exported Symbols File" at it.
After building, if I run "nm" on the resulting plugin, I still see tons
and tons of symbols, but it now loads up without conflict with my older
plugin which previously conflicted.
I expected to see only those few initWithAPIManager: symbols in the nm
results. Can someone explain why I'm still seeing everything? Can I get
rid of the rest of the symbols some other way?
_______________________________________________
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