Re: Universal Shared libraries
Re: Universal Shared libraries
- Subject: Re: Universal Shared libraries
- From: Mark Thomas <email@hidden>
- Date: Mon, 20 Mar 2006 16:29:30 +0000
- Organization: Coderus Ltd
Hi,
From my previous post asking about universal Shared libraries and .dylibs.
I wonder if the same also stands true for lib<fsp>.a as well for universal
static libraries, as doing a quick test with a new project in Xcode 2.2.1
seems to imply this as well.
So I guess the question is should lib<fsp>.a be provide as a universal
static library or should you provide a separate ppc and i386 versions. I
already provide gcc33 versions of my lib's.
Any thoughts are great or any advantages disadvantages ?, I see that
providing a single .a should be easier for the build system as the linker
will pull the correct code fragment out of lib<fsp>.a.
Thanks
Mark.
_______________________________________________
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