• 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
Framework header conversion advice
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Framework header conversion advice


  • Subject: Framework header conversion advice
  • From: Glen Low <email@hidden>
  • Date: Sat, 5 Jun 2004 11:13:32 +0800

Dear All,

As you know, in OS X framework headers are #included like this <Framework/Header.h>. Unfortunately this is pretty different from standard Unix usage (LSB/FSH) where the headers are put into /usr/include and used like this <Header.h>. So I have an open source project (no guesses here -- it's Graphviz) and I'm readying its platform-neutral headers to be put into OS X frameworks -- the previous versions I released were missing the headers -- and I'm faced with the issue of internal includes.

E.g. suppose one.h includes two.h in the same framework.

Using LSB/FSH conventions, it would written as
#include <two.h>

Using OS X framework conventions, it would be written as
#include <framework/two.h>

If I distribute headers using the original LSB/FSH style, the resulting framework can't be used directly.

Some advice would be good:

1. I could convince the authors to install in /usr/include/dotneato instead of /usr/include/, which has the coincidental value of making the headers look like <dotneato/header.h>, which is compatible with OS X framework includes. Not very likely though.

2. I could convince them to use "header.h" instead of <header.h>, which seems to work fine too. Also not very likely...

3. I could fence the internal includes like this:
#ifdef __APPLE__
#include <framework/two.h>
#else
#include <two.h>
#endif

4. I could run a sed script phase to weed out the <two.h> and change to <framework/two.h>.. Not entirely ideal either since it doesn't use the Xcode inbuilt header machinery...

5. Leave it as is and ask users to also -I Framework/Headers.

Any other suggestions?


Cheers, Glen Low


--- pixelglow software | simply brilliant stuff www.pixelglow.com _______________________________________________ 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: Framework header conversion advice
      • From: Arturo PĂ©rez <email@hidden>
  • Prev by Date: getting CHUD examples to run: error 44e
  • Next by Date: XCode issue (wants to use the wrong Info.plist file)
  • Previous by thread: Re: getting CHUD examples to run: error 44e
  • Next by thread: Re: Framework header conversion advice
  • Index(es):
    • Date
    • Thread