• 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
visibility weirdness...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

visibility weirdness...


  • Subject: visibility weirdness...
  • From: "Jeff Roberts" <email@hidden>
  • Date: Sun, 17 Sep 2006 09:52:31 -0700
  • Organization: RAD Game Tools

I'm using gcc on macos x86, and I can't seem to get my non-public functions to be not exported in a dylib. So, there are three visibility levels:

1) static functions (these aren't seen, so they are working).
2) functions visible to other OBJs within the dylib (these are what I'm trying to hide)
3) exported functions (these are working).


I'm compiling using -fvisibility=hidden, and my exported functions use __attribute__((visibility("hidden"))). The exported functions work fine, and static functions work great, but nm still shows those 2nd kind of symbols (and they still get called through the sylib stub functions...

->Jeff


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Prev by Date: Re: why does this code NOT work on macbookpro?
  • Next by Date: Re: visibility weirdness...
  • Previous by thread: Re: why does this code NOT work on macbookpro?
  • Next by thread: Re: visibility weirdness...
  • Index(es):
    • Date
    • Thread