Re: Compiling cctools in Codewarrior/PEF
Re: Compiling cctools in Codewarrior/PEF
- Subject: Re: Compiling cctools in Codewarrior/PEF
- From: Josh <email@hidden>
- Date: Mon, 18 Oct 2004 10:14:14 -0500
Shantonu,
Thanks for the tips. I'll take a look at the odcctools project. There
are a couple of reasons I don't want to include it as a framework.
First of all, size is of the utmost importance so I wanted to have it
statically linked into my executable and rely on the linker to strip
out the dead code (I'm not even sure how well Codewarrior's linker
does this, as I haven't gotten far enough to test this out). Second of
all I didn't want to require a file on the user's system. In
retrospect, the second isn't as big a problem (since my CFM app is
bundled) as the first.
Man, I'm dying to move to Mach-O! Unfortunately, the project I'm
working on is several years old and has millions of lines of code that
would take entirely too long to port over to Mach-O.
Josh Ferguson
On Mon, 18 Oct 2004 07:38:27 -0700, Shantonu Sen <email@hidden> wrote:
>
> On Oct 18, 2004, at 6:55 AM, Josh wrote:
>
> > <sorry if this is a repost - I didn't see it posted the first time I
> > emailed it...>
> >
> > I'm trying to compile the some of the prebinding libraries included in
> > cctools using Codewarrior. Ultimately, I want to call unprebind() from
> > a Carbon CFM app. The problem is that it compiles as a Mach-O static
> > library (and I need it to be static) and I can't call that from a CFM
> > app.
>
> Why can't you compile it as a bundle and load that? I believe that is
> the
> supported way of calling Mach-O code from CFM apps, no?
>
> > The other option is to compile it as a Carbon PEF library, but I
> > can't get codewarrior to do this (mwpefcc gives me all sorts of errors
> > with the #include statements).
>
> What kind of errors? If it's problems with the #import statements, you
> may
> want to take a look at the odcctools project
> <http://www.opendarwin.org/projects/odcctools/>,
> which maintains a set of patches against cctools. for greater
> portability
> and ease of building. You probably want to apply the patches to some
> version of cctools released by Apple in a developer tools release,
> unlike
> the cctools snapshots they currently use.
>
> > Anyone have any experience or tips with
> > this?
>
> Not really. Most developers have moved to Mach-O.
>
> Shantonu
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden