Forcing G++ for linking?
Forcing G++ for linking?
- Subject: Forcing G++ for linking?
- From: Nick Zitzmann <email@hidden>
- Date: Mon, 19 Sep 2005 22:18:11 -0600
I've checked the archives and I didn't see an answer to this question...
Short version: How do I force Xcode to use G++ to link a binary
instead of GCC? Is that even possible?
Long version: I have a static library that includes some C++ code.
The static library was compiled by me using GCC 4.0. I want to link
the static library to another project, which does not contain any C++
code. It is also being compiled with GCC 4.0. So far I've made the
project build by including the libstdc++ dylib directly, but every
time I link the project, I always get a warning about "multiple
definitions of symbol ___eprintf". I think that's a harmless warning,
but I'd like to get rid of it, and I'd like to try getting rid of it
by making Xcode link the project using G++ instead of GCC. But I
can't find an option that controls this. I already tried passing the
compiler option "-x c++" to the linker, and it doesn't work. Does it
exist? If so, where is it?
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