Re: [PARTIALLY SOLVED]Re: Forcing G++ for linking?
Re: [PARTIALLY SOLVED]Re: Forcing G++ for linking?
- Subject: Re: [PARTIALLY SOLVED]Re: Forcing G++ for linking?
- From: Nick Zitzmann <email@hidden>
- Date: Tue, 20 Sep 2005 21:17:48 -0600
On Sep 20, 2005, at 8:38 PM, Eric Albert wrote:
libgcc.a should only get pulled in by things which are building
with gcc 3.3, and you probably don't want to mix static libraries
built with 3.3 with products built with 4.0. I'd suggest making
sure that you're using the same compiler version for all pieces of
your project.
I just verified that both the static library and the bundle are being
built with GCC 4. Still, GCC 4 is linking them to both libgcc.a and
libgcc_s.dylib, and I verified this by using the fs_usage tool. One
thing I thought of is I'm using the "-all_load" linker option so that
it imports all of the static library. Otherwise, several ObjC
instance methods go missing in the final linked product.
Again, the only workaround for this issue that I've found is to use
the -nostdlib linker option and manually link in the system
libraries. Is there another way?
Nick Zitzmann
<http://seiryu.home.comcast.net/>
S/MIME signature available upon request
_______________________________________________
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