Exporting Symbols...
Exporting Symbols...
- Subject: Exporting Symbols...
- From: Dave Thorup <email@hidden>
- Date: Fri, 22 Jul 2005 10:46:56 -0400
Is using an Exported Symbols File really the only way to control what
symbols are exported with Xcode 2.1 and GCC 3.3? Is GCC 4.0 any better?
If this really is the only way to control exported symbols then it
really seems like a giant step backwards to the stone age of
computers. Why not just specify the exported symbols with Punch
Cards? That wouldn't be too much harder.
In CodeWarrior all you need to do is:
#pragma export on
// define your functions, globals, etc.
#pragma export off
How easy is that? I don't think it gets any easier. Even on Windows
with VC++ all you need to do is prepend things with "__declspec
(dllexport)". Not quite as easy as CodeWarrior, but light-years
ahead of GCC.
Please don't tell me that I'm going to have to use nm to sort through
thousands of lines of symbols to try and figure out what is and isn't
going to be exported in half a dozen libraries (most of which I
didn't write or design). I'd rather chew on glass.
Hasn't anyone tried to automate this by parsing source files and
automatically generating the exported symbols based on pragmas or
"__declspec(dllexport)"?
_____________________________
Dave Thorup
Software Engineer
email@hidden
http://www.kuwan.net
Defaults Manager - The premier editor for Mac OS X's User Defaults /
Preferences database.
_______________________________________________
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