Re: Exporting Symbols...
Re: Exporting Symbols...
- Subject: Re: Exporting Symbols...
- From: Dave Thorup <email@hidden>
- Date: Fri, 22 Jul 2005 13:44:43 -0400
On Jul 22, 2005, at 12:27 PM, Chris Espinosa wrote:
Try the visibility attributes in gcc 4.0. They're meant to be
parallel to __declspec. In fact you can define a macro that
expands to __declspec(dllexport) on Windows and __attribute__
((visibility("default"))) on Mac.
http://developer.apple.com/documentation/DeveloperTools/Conceptual/
CppRuntimeEnv/Articles/SymbolVisibility.html
Thanks for the info on GCC 4. There are also pragmas that can be used:
#pragma GCC visibility push(default)
void g() { }
void h() { }
#pragma GCC visibility pop
This might be easier for us since it works more like the CodeWarrior
method.
This is all great for GCC 4.0, but what about those of us that need
to support Mac OS X 10.2.0? C++ binaries built with GCC 4.0 can only
run on 10.3.9 and later. Until you make it so that GCC 4.0 supports
10.2.0 and later we will not be able to use it.
So, is there any other way (besides an exported symbols file) to
export symbols with GCC 3.3?
Thanks
_____________________________
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