[Camelbones-devel] ANN: CamelBones 0.3-pre3

[Sherm P. <sh...@do...>]

On Monday, July 14, 2003, at 01:53 AM, Thilo Planz wrote:

> the list has been awfully quiet after this announcement.

Maybe a new announcement will shake things up... ;-)

I've uploaded a new -pre3 release to my site: <http://www.dot-app.org>.

> I had the exact same error messages (or rather compile warnings) as 
> with pre1

I downloaded the April 2002 beta tools for 10.1, which are as close as I 
can get to the Jaguar tools. After closely reading the license, I found 
that the licensing wasn't as restrictive as I'd feared - The GCC3.1 
that's included with that release is considered a beta, and releasing 
binaries built with it isn't allowed, but that's the only restriction. I 
can release .pbprj projects that were created with that release of 
Project Builder 2.

Using that release of GCC 3.1, I was able to duplicate and address the 
build problems you reported - namely, the complaints about variables 
being automatically promoted when passed through a varargs call, and the 
precompiled header warnings. It now compiles cleanly for me, using 
either 2.95.2 or 3.1. I haven't tried 3.3 yet - although I did receive 
an email from Apple telling me that a Panther CD is on its way... ;-)

I silenced the warnings about precompiled headers by the simplest means 
possible - I added a compiler option that disables precompiled headers. 
The source of the problem is a conflict between the Perl headers and 
Carbon.h, neither of which I can easily fix. Since the problem caused 
precompiled headers to be unusable anyway, I didn't see a noticable 
difference in build time.

> I am also uncertain if libffi works for me at all.
> Sherm says it should be included in Jaguar's gcc, but I could not find 
> header files for it.

This is bordering on the bizarre - I couldn't find it in the GCC 3.1 
libraries I installed either.

And yet, the code for the libffi version I included in the last release 
was obtained from the GCC3 folder in opendarwin.org's CVS. The web site 
for the stand-alone libffi distribution indicates that it is only needed 
versions of GCC prior to 3.0. And, the last time I installed GNUStep 
under Linux, the docs for that indicated that a separate libffi install 
was only needed if one were not using GCC 3 or newer. All of the 
documentation that I can find implies that it should be there.

Whatever. Irrespective of whether or not it *should* be installed, all 
the evidence seems to indicate that it's not. So, I've integrated it 
into the CamelBones build tree - it's no longer necessary to build and 
install it as a separate library.

> So I installed the one provided with pre1.

You probably should delete that, to avoid conflicts. Delete 
${prefix}/lib/libffi* and ${prefix}/include/ffi.h, where $prefix is the 
installation prefix you used - /usr/local is the default.

I'm flying out to CA early tomorrow (Tuesday) for a job interview, and I 
won't be back home until very late Friday night. I'll probably have a 
pile of email waiting for me, so you may not hear from me until this 
time next week.

sherm--

"I have no special gift, I am only passionately curious." - Albert 
Einstein