• 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: Markus Hitter <email@hidden>
  • Date: Sat, 15 Nov 2003 09:18:18 +0100

Am 14.11.2003 um 18:26 schrieb George Warner:

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/.

Hmm -

2) or $HOME/Library/Frameworks if you want to have it installable without admin rights.

3) Include the Framework to every app and, on consecutive installations, let the Installer symlink the framework to the one installed with the first app instead of installing a duplicate. If done with hard links, you even can remove the first installation and the files stay in place for the second app.


Am 14.11.2003 um 20:36 schrieb Dave Rehring:

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.

I'm not aware of any technical reason for such a requirement. In Principle, you can install a framework anywhere. One reason for using the standard paths is to have all frameworks grouped nicely, i.e. Drag 'n Drop installable. Reason #2 is, runtime/Foundation/AppKit methods will look up standard places by default, only. Using non-standard places requires extra logic for finding the frameworks. Unneccesary headaces on most cases.



Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
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>
    • Re: Managing executable frameworks for multiple projects
      • From: Dave Rehring <email@hidden>
References: 
 >re: Managing executable frameworks for multiple projects (From: George Warner <email@hidden>)

  • Prev by Date: Re: porting code from project builder to xcode
  • Next by Date: Re: Getting Started with CVS in Xcode
  • Previous by thread: Re: Managing executable frameworks for multiple projects
  • Next by thread: Re: Managing executable frameworks for multiple projects
  • Index(es):
    • Date
    • Thread