zoolib-dev

[ZooLib-dev] Mach-O executable format?

[Michael D. C. <cra...@go...>]

We discussed a while back about supporting the Mach-O executable format on Mac 
OS X.  Is this working all the way yet?

What I've been doing is building a CFM application, and then using the DTS 
sample code CallMachOFramework to call OS X-specific functions.

Calling the functions that way works fine, but it makes it really ugly to build 
my application.  The problem is that CodeWarrior doesn't support the framework 
style header files in a CFM application.

That is, something like #include <IOKit/IOTypes.h> won't compile because 
IOTypes.h is not in a folder named IOKit - it's in a folder named Headers, and 
that's in a folder named IOKit.framework.

When you build a Mach O application, the compiler is hacked to process the 
#include file the way you need, but not when you build a CFM application.

The approach I have taken is to copy the headers out of the framework folders 
and put them in my project folders, nested in a folder with the right name.  So 
I can create folders where #include <IOKit/IOTypes.h> will work.  But it's a 
horrible hack, takes up lots of disk space and makes me really unhappy.

The best solution for what I'm doing right at the moment would be to build a 
Mach-O zoolib application (I finally got CodeWarrior 8).

I would still be interested to know how to deal with the headers from a CFM 
application though because I have another application where I would still like 
to use CallMachOFramework.

Thanks for your help,

Mike
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
cra...@go...

      Tilting at Windmills for a Better Tomorrow.

Re: [ZooLib-dev] Mach-O executable format?

[Joshua J. <wan...@me...>]

--On Monday, March 31, 2003 10:18 AM -0500 "Michael D. Crawford" 
<cra...@go...> wrote:

> That is, something like #include <IOKit/IOTypes.h> won't compile because
> IOTypes.h is not in a folder named IOKit - it's in a folder named
> Headers, and that's in a folder named IOKit.framework.
>
> When you build a Mach O application, the compiler is hacked to process
> the #include file the way you need, but not when you build a CFM
> application.
>
> The approach I have taken is to copy the headers out of the framework
> folders and put them in my project folders, nested in a folder with the
> right name.  So I can create folders where #include <IOKit/IOTypes.h>
> will work.  But it's a horrible hack, takes up lots of disk space and
> makes me really unhappy.

There's no need to copy the files.  You can use symlinks/aliases, or fake 
headers that include the original in its real location:  e.g.
#include <IOKit.framework/Headers/IOTypes.h>

I hope this helps.

Josh