• 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: Frameworks in HOME/Library, why?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Frameworks in HOME/Library, why?


  • Subject: Re: Frameworks in HOME/Library, why?
  • From: Ondra Cada <email@hidden>
  • Date: Tue, 21 May 2002 22:31:57 +0200

On Tuesday, May 21, 2002, at 09:12 , Paul Cezanne wrote:

I have a set of code that I've put into a Framework.

I have a Cocoa app that calls into this Framework.

This all works fine except I'm bothered by one thing. I have to COPY my Framework into $HOME/Library/Frameworks.

Is it really supposed to behave like this? Aside from being annoying from an installation standpoint, it bugs me as a developer, I can't even put an alias there so when I update the Framework I must copy it there.

You can use a softlink. Aliases work with Carbon only.
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
2K Development: email@hidden http://www.2kdevelopment.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Frameworks in HOME/Library, why? (From: Paul Cezanne <email@hidden>)

  • Prev by Date: Re: Obj-C, class methods and instance methods
  • Next by Date: Re: Getting 'mouseMoved' events
  • Previous by thread: Frameworks in HOME/Library, why?
  • Next by thread: Cocoa Document-Based Applications
  • Index(es):
    • Date
    • Thread