• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: C++ name collisions between plugins
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: C++ name collisions between plugins


  • Subject: Re: C++ name collisions between plugins
  • From: Stephen Bash <email@hidden>
  • Date: Thu, 15 Aug 2013 14:19:06 -0400 (EDT)

----- Original Message -----
> From: "Paul Miller" <email@hidden>
> Sent: Thursday, August 15, 2013 2:07:21 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).

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).

Good luck!

Stephen
 _______________________________________________
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


  • Follow-Ups:
    • Re: C++ name collisions between plugins
      • From: Paul Miller <email@hidden>
References: 
 >Re: C++ name collisions between plugins (From: Paul Miller <email@hidden>)

  • Prev by Date: Re: C++ name collisions between plugins
  • Next by Date: FCP-X and MPEG files
  • Previous by thread: Re: C++ name collisions between plugins
  • Next by thread: Re: C++ name collisions between plugins
  • Index(es):
    • Date
    • Thread