Re: GCC 4.0.x, bundle-loader and C code
Re: GCC 4.0.x, bundle-loader and C code
- Subject: Re: GCC 4.0.x, bundle-loader and C code
- From: Eric Albert <email@hidden>
- Date: Thu, 22 Dec 2005 09:41:17 -0800
On Dec 22, 2005, at 4:05 AM, Stephane Sudre wrote:
Is there any new option by default with XCode 2.2 & GCC 4 which could
explain that some symbols are not found when building a project?
I have 2 projects :
o Project A is a Cocoa application using both Objective-C and C++ code.
Project A is building fine as a Universal Binary (PPC Deployment
Target is 10.2, Intel Target Deployment Target is 10.4)
o Project B is a Cocoa bundle which is a plug-in for Project A. It
contains Objective-C and C code.
Project B is using the bundle-loader options for both Objective-C and
C/C++ code.
Project B is not building fine as a Universal Binary (PPC 10.2
Deployment Target works, Intel 10.4 Target does not work).
The problem with the Intel target is that some symbols are said not to
be found.
The new option is "Symbols Hidden by Default", which ensures that no
symbols are exported unless they're explicitly marked as being
exported. See
<http://developer.apple.com/documentation/DeveloperTools/Conceptual/
CppRuntimeEnv/Articles/SymbolVisibility.html> for some documentation
about this at the compiler level. I think there's additional
documentation in the Xcode docs.
I'd suggest explicitly exporting the symbols from your application that
the bundle needs to link against rather than turning off the "Symbols
Hidden by Default" setting, since the fewer symbols you export the
better your application will perform (not by much, but every little bit
helps when it comes to performance).
Hope this helps,
Eric
_______________________________________________
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