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 09:53:45 -0800
on 11/14/03 9:46 AM, tobias at <email@hidden> wrote:
> As opposed to ~/Library/Frameworks ? Or maybe a there's a network
> share that is kept up to date by a build machine that the users connect
> to. This question is more about managing internal distribution of
> libraries across multiple users/accounts/machines. What's the system
> that is used internally?
>
> On Nov 14, 2003, at 11:26 AM, George Warner wrote:
>
>> On Thu, 13 Nov 2003 23:49:22 -0600, tobias <email@hidden> wrote:
>>> I'm building executable based frameworks that are meant to be shared
>>> across a suite of applications. I would like to copy these to a
>>> common
>>> directory that users of these frameworks can then access to add them
>>> to
>>> their projects. Where should this place be? Is there a standard way
>>> to manage this? Any suggestions?
>>
>> There is really only one answer to this question: /Library/Frameworks/.
>>
>> /System/Library/Frameworks belongs to Apple. ;-)
Shared across a suite of application == [~]/Library/Frameworks.
Users (plural) == it shouldn't be in ~.
Developers & users (or their admin) should install your framework on their
machines.
I'm putting together a "Where it should go" technote that includes a lot of
the previously unstated reasoning behind these recommendations. I hope to
have it finished before the end of the year.
--
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.