Re: Managing executable frameworks for multiple projects
Re: Managing executable frameworks for multiple projects
- Subject: Re: Managing executable frameworks for multiple projects
- From: George Warner <email@hidden>
- Date: Fri, 14 Nov 2003 15:46:49 -0800
on 11/14/03 11:36 AM, Dave Rehring at <email@hidden> wrote:
> Actually, isn't it fairly non-standard to support having a framework at a
> non-fixed path [in that the developer/application code would be responsible
> for finding, loading and accessing it].
True, but /Library/Framework is a fixed location. It's where it should be to
be built against and where it should be run from.
> My understanding of frameworks is that if you add them to your project, the
> framework either needs to be at that same location or with one level of
> redirection using the @executable [well something like this] hack.
If you put it in your application bundle then you have to set the install
path to @executable/../Frameworks.
> It's not like Apple's support of CFM/PEF where the library had a name to
> link against and the system searched a number of folders in a specific order
> to find the library.
True. Welcome to Mac OS X. ;-)
--
Enjoy,
George Warner,
Schizophrenic Optimization Scientists
Apple Developer Technical Support (DTS)
_______________________________________________
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.