Re: Static Library Equivalent of a Framework?
Re: Static Library Equivalent of a Framework?
- Subject: Re: Static Library Equivalent of a Framework?
- From: "Timothy J. Wood" <email@hidden>
- Date: Tue, 18 Nov 2003 12:16:28 -0800
On Tuesday, November 18, 2003, at 11:08 AM, Jim Ingham wrote:
Another option would be to cons up a dummy dylib for the framework
that does get loaded, but doesn't expose any of the API's in the
framework. This would suffice to locate the bundle and its associated
resources. I think this would be a better option than trying to
handle merging resources since avoiding duplicates could get tricky...
That's an interesting idea...
We'd still have to modify our source, though. The 'static library +
copied resources' case makes sure that '[NSBundle
bundleForClass:[MyClass class]]' will continue to work. We often use
this to find resources associated with a particular class rather than
looking up bundles by name.
-tim
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.