Frameworks in HOME/Library, why?
Frameworks in HOME/Library, why?
- Subject: Frameworks in HOME/Library, why?
- From: Paul Cezanne <email@hidden>
- Date: Tue, 21 May 2002 15:12:27 -0400
I'm new to Cocoa/ProjectBuilder and I have a question which may not even be a Cocoa/PB question, so I apologize in advance it it this isn't an appropriate forum.
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. (And yes, I know, I could have that as part of the copy build phase, it is still just annoying.)
Is there a way around this? I don't need this code to be dynamically loaded, one framework, one app.
Thanks!
Paul
_______________________________________________
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.