• 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: "Kyle Sluder" <email@hidden>
  • Date: Sun, 13 Jan 2008 03:55:41 -0500

Assuming you're building your framework as part of the same project as
your actual app, you can simply mark the role of the framework's
header files as private, and #import them in your app's source using
relative quoted paths like #import "FrameworkHeaderFile.h", rather
than the typical #import <FrameworkName/HeaderFile.h> paradigm.

You're still going to need to link the app to the framework and copy
the framework into the app bundle's Frameworks directory, but this way
you won't be copying the headers with it.

HTH,
--Kyle Sluder
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Private Frameworks
      • From: Chris Hanson <email@hidden>
References: 
 >Private Frameworks (From: "Mitchell Hashimoto" <email@hidden>)

  • Prev by Date: Private Frameworks
  • Next by Date: Re: Garbage collection problem
  • Previous by thread: Private Frameworks
  • Next by thread: Re: Private Frameworks
  • Index(es):
    • Date
    • Thread