Re: visibility weirdness...
Re: visibility weirdness...
- Subject: Re: visibility weirdness...
- From: Eric Albert <email@hidden>
- Date: Sun, 17 Sep 2006 13:25:33 -0700
Are you building your dylib without -single_module? Calls between
modules go through dylib stubs, but calls within a single module
don't have to. -multi_module is the default in the linker, but I'm
not sure what the Xcode templates use by default.
Hope this helps,
Eric
On Sep 17, 2006, at 10:59 AM, Jeff Roberts wrote:
Little more info. When I use nm to list the symbols, adding the -
fvisibility=hidden does change the type of symbol listed from "T"
to "t" which does mean local, but when I call one of these symbols,
it still goes through the dylib_stub stuff instead of directly
calling the function.
->Jeff
----- Original Message ----- From: "Jeff Roberts"
<email@hidden>
To: <email@hidden>
Sent: Sunday, September 17, 2006 9:52 AM
Subject: visibility weirdness...
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:
40outofcheese.org
This email sent to email@hidden
_______________________________________________
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