• 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: private frameworks
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: private frameworks


  • Subject: Re: private frameworks
  • From: Todd Ditchendorf <email@hidden>
  • Date: Tue, 1 Nov 2005 09:13:47 -0600

Niko! I ran into the very same problem for the first time a few weeks ago too! I struggled for a few days reading the docs you referenced below, and then found an awesome tutorial by an independent Mac developer that answered all my questions, and got me on track in minutes.

Jonathan ‘Wolf’ Rentzsch

http://rentzsch.com/cocoa/embeddedFrameworks

This includes a wonderful video screencast to show you how to get it all set up in Xcode. This guy's amazing.

GOOD LUCK!!!!

Todd Ditchendorf






On Nov 1, 2005, at 3:12 AM, Niko Matsakis wrote:

I have a utility Framework I have developed that I wish to include in an application of mine as a private framework. I have read the "Framework Programming Guide" and tried tof follow its directions but they don't seem to work.

I did deviate from the guide in one respect: it recommends adding the Framework's source into your application project: this strikes me as a good idea if this framework is only used by one application, but if it is used by many then it makes more sense to have a separate project for the Framework itself. If this is wrong, let me know, but it seems like otherwise there will be configuration for the same framework duplicated among many different projects.

Anyhow, what I tried eventually is to add a "copy files" step to my project which copies the referenced Oaxaca.framework into the Frameworks directory of the application. I have verified in Terminal that the file is present. This seems to be what the Framework Programming Guide suggested, although they said to do it via the "install path" from the framework target. As the framework target is not in my project, I thought I'd try a different route.

Unfortunately, it doesn't work.  Any advice?

What I don't want is for users to have to install the Framework separately from the Application. I definitely want the Application to be self contained.


Niko _______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >private frameworks (From: Niko Matsakis <email@hidden>)

  • Prev by Date: Re: thread and run loop
  • Next by Date: Re: private frameworks
  • Previous by thread: Re: private frameworks
  • Next by thread: Re: private frameworks
  • Index(es):
    • Date
    • Thread