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: Thu, 22 Sep 2005 20:22:48 -0600
On Sep 20, 2005, at 10:40 PM, Chris Espinosa wrote:
Did you even try the "Compile Sources As" build setting, which lets
you say that a .c or .m file is actually C++?
No, but I found that setting the LD build setting as Eric A.
suggested to "/usr/bin/g++" worked.
Now I'm running into a number of duplicate symbol warnings, because
for whatever reason (I'm guessing the libraries are not 100%
identical), G++ is linking the binary using both the static and
shared versions of libgcc, and I'm linking using the "-all_load"
linker option, which has the side effect of trying to combine the two
libraries. Unfortunately I need to use that option, because otherwise
the linker doesn't include an important piece of Objective-C code in
a static library, and I wind up getting "selector not recognized"
exceptions when the plugin is working. I can't find a workaround that
doesn't end up producing a broken build in one architecture or another.
I can't find any documentation suggesting that a more selective
version of the "-all_load" option exists. Is there such a thing, or
should I file an enhancement request?
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