On Aug 15, 2013, at 11:07 AM, Paul Miller <paul@fxtech.com> wrote:
On 8/15/2013 12:40 PM, Stephen Bash wrote:
----- Original Message -----
From: "Paul Miller" <paul@fxtech.com> Sent: Thursday, August 15, 2013 1:32:39 PM Subject: Re: C++ name collisions between plugins
I'm using Intel 12.0, for reasons relating to OpenMP. Another developer suggested I try setting "-fvisibility-hidden=filename", which I will try next.
Just to be clear, the filename here is a text file listing the symbols to hide, not the source or object file being compiled.
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).
You can do that. There's a setting for both "exported symbols" and "unexpected symbols" in the target settings of the Xcode project. So you can use either a white list or a black list, and I think there's even a way to do both at the same time if you need to for some reason. Darrin _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com