• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Managing executable frameworks for multiple projects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Managing executable frameworks for multiple projects


  • Subject: Re: Managing executable frameworks for multiple projects
  • From: Dave Rehring <email@hidden>
  • Date: Fri, 14 Nov 2003 11:36:19 -0800

On 11/14/03 9:53 AM, George Warner 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 ~.
>
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].

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.

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.

Later,
--
David Rehring                  Psychos do not explode when light hits
VP of Research and Development them, no matter how crazy they are...
Atimi Software, Inc.
www.atimi.com                  And totally insane guy!
_______________________________________________
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.

  • Follow-Ups:
    • Re: Managing executable frameworks for multiple projects
      • From: George Warner <email@hidden>
References: 
 >Re: Managing executable frameworks for multiple projects (From: George Warner <email@hidden>)

  • Prev by Date: Getting Started with CVS in Xcode
  • Next by Date: Perforce Just Crashes?
  • Previous by thread: Re: Managing executable frameworks for multiple projects
  • Next by thread: Re: Managing executable frameworks for multiple projects
  • Index(es):
    • Date
    • Thread