• 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: Umbrella Frameworks and headers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Umbrella Frameworks and headers


  • Subject: Re: Umbrella Frameworks and headers
  • From: Nick Zitzmann <email@hidden>
  • Date: Mon, 12 Jul 2004 11:18:00 -0600

On Jul 12, 2004, at 9:08 AM, Bryan Pietrzak wrote:

If add an umbrella framework like ApplicationServices to my project and then do an #include <ApplicationServices/ApplicationServices.h> should I then be able to expect that ALL headers within the umbrella framework, including those in sub-frameworks are available without any additional effort in Xcode? If so, then the fact that PrintCore.h does not include PMTicket.h is clearly a bug.

Most of them, anyway. Stuff that is needed for everyday use should be part of the main header. The only other framework header I'm aware of that isn't included in the master header is Foundation's NSDebug.h, and I can understand why, because it's supposed to be used for debugging purposes only...


So if PMTicket.h is supposed to be available for "everyday use", then I would recommend filing a bug report on that. Chances are someone overlooked that header when they were writing PrintCore.h, but there's no way to be sure until a bug report is filed.

If not, then I don't understand exactly what the Right Thing to do in Xcode is with regard to these "orhpaned" headers within frameworks. Is adding a sub-framework or adding a search path as above the Right Thing?

I think adding the search path is the right way to do this right now. I wouldn't make the project depend on an framework within another framework's umbrella, since those could be moved around between OS releases. I remember Metrowerks did this with MetroNub in CodeWarrior Pro 6, which basically made it impossible to run the debugger in versions of Mac OS X other than the public beta, because it depended on CarbonCore.framework, and Apple moved that framework's location from where it was in the public beta... Although a symbolic link could probably fix that, how many of one's end users are going to figure that one out?


Nick Zitzmann
<http://seiryu.home.comcast.net/>
S/MIME signature available upon request

"Monsieur l'abbi, I detest what you write, but I would give my life to make it possible for you to continue to write." - Voltaire
_______________________________________________
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: Umbrella Frameworks and headers
      • From: Bryan Pietrzak <email@hidden>
References: 
 >errors trying to compile with PMTicketRef (From: Bryan Pietrzak <email@hidden>)
 >Re: PMTicketRef and Frameworks (From: Bryan Pietrzak <email@hidden>)
 >Re: PMTicketRef and Frameworks (From: Nick Zitzmann <email@hidden>)
 >Re:Umbrella Frameworks and headers (From: Bryan Pietrzak <email@hidden>)

  • Prev by Date: re: "crossing the user-session boundary", or "the mythical TN2077"?
  • Next by Date: Re: Umbrella Frameworks and headers
  • Previous by thread: Re:Umbrella Frameworks and headers
  • Next by thread: Re: Umbrella Frameworks and headers
  • Index(es):
    • Date
    • Thread