Re: Link Error: Undefined symbols: typeinfo for ... in XCode 2.0
Re: Link Error: Undefined symbols: typeinfo for ... in XCode 2.0
- Subject: Re: Link Error: Undefined symbols: typeinfo for ... in XCode 2.0
- From: Chris Espinosa <email@hidden>
- Date: Tue, 17 May 2005 13:25:47 -0700
On May 17, 2005, at 12:39 AM, Dieter Oberkofler wrote: I'm trying to (re)build a C++ application in XCode 2.0 that was compiling and linking just fine in XCode 1.5 and get the following linker error message: ... Undefined symbols: typeinfo for PWR_CApplication typeinfo for PWR_CWindow collect2: id returned 1 exit status Build failed... The symbols PWR_CApplication and PWR_CWindow are C++ classes that (at least) when compiled with XCOde 1.5 seem to exist in a 3rd party library I'm including as a framework and collect2 does not show up as a symbol in any of the files of my project.
1) Has someone an idea what the source of this problem might be or what to look for?
If the third-party library was compiled with CodeWarrior or gcc3.3, and you're trying to link it with an app compiled with 4.0, this is not unexpected. Select your application Target, choose Get Info, click the Rules tab, and set your compiler to gcc 3.3 for that target.
2) Should a framework that did work together with XCode 1.5 also work with XCode 2.0?
If you use the same compiler, yes.
3) Can XCode 2.0 and 1.5 run on the same hardware without to many problems?
On the same hardware, yes; on the same OS, no. They rely on a common set of OS libraries, tools, and frameworks that change each OS release. Some of these are abstracted so that they're switchable (like gcc); most are not. If you have a machine that can boot between Panther and Tiger, you can have 1.5 on Panther and 2.0 on Tiger on the same machine, but not running at the same time.4) Can I actually use XCode 1.5 under Tiger?
No. There are a large number of underlying changes in the OS that break Xcode 1.5 when running on Tiger. 5) Is it generally adviced to use XCode 2.0 or is it just to new?
We advise it, or else we wouldn't have shipped it. With backwards-compatible compiler selection and SDK support you should be able to upgrade your projects to build with Xcode 2.0 in a short period of time, and get the benefits of a faster development environment with more features and (hopefully) fewer bugs.
Regards,
Chris |
_______________________________________________
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