Re: strange link error: ld: Undefined symbols: _sprintf$LDBLStub
Re: strange link error: ld: Undefined symbols: _sprintf$LDBLStub
- Subject: Re: strange link error: ld: Undefined symbols: _sprintf$LDBLStub
- From: "Sean McBride" <email@hidden>
- Date: Thu, 18 Aug 2005 10:28:43 -0400
- Organization: Rogue Research
On 2005-08-18 11:03, Bill Northcott said:
>Basically you cannot link objects produced by gcc compilers with
>different major versions.
Even when working with pure C? (ie I know C++ name mangling changes
between compilers)
>This is one reason why static libraries
>are deprecated on MacOS X.
'deprecated' as in "discouraged and going away"? Surely not?! Where
does it say this?
>The only one distributed by Apple are
>safely buried in the versioned areas of the gcc library tree. If you
>use dynamic libraries, it makes no difference what compiler they were
>built with. Static libraries should only be used as intermediate
>convenience libraries included in a larger build process using one
>compiler throughout.
Alas, these 3rd party libraries build as static libraries. But for the
moment, let's assume I could build them as dylibs. Can I put a .dylib
in my .app bundle? Or does the .dylib have to be installed somewhere
like /usr/lib/? I seem to remember that only .frameworks can go in
application bundles. I like static libs because they are built right
into my app, which allows me to have a drag-installable application.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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