Re: Static-linking a framework?
Re: Static-linking a framework?
- Subject: Re: Static-linking a framework?
- From: Uli Kusterer <email@hidden>
- Date: Thu, 6 Mar 2008 00:37:16 +0100
Am 05.03.2008 um 22:24 schrieb Kai:
No, unfortunately I do not know how to achieve your goal. I just
want to second you that this is a very desirable feature. I would
appreciate it if you could keep me updated in case you find a
solution.
I tried a few venues, but none really work. While you can of course
generate a static library and just put some folders with the resources
it needs next to it, you still have to manually keep them synched with
all applications that use them.
A framework essentially pulls in all resources and headers in its
folders at build time, and Xcode's project search will even find in
them. I tried using a folder reference for the resources, but while
they get updated, they also end up in a subfolder, which causes
problems for retrieving localized strings.
One could probably also create an umbrella header, which would let
you simply include that one header and add the header folder as an
include path, but for one that's a lot of manual maintainance, and
second you wouldn't see the headers included by the umbrella header in
project searches.
So, in the end I filed a bug, and I'm hoping Apple will implement
support in Xcode for automatically scanned header and resource folders
at least, or even full-blown static frameworks. The nice part is that
this could all happen in Xcode, no need to change any runtimes,
dynamic loaders or linkers...
Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
_______________________________________________
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