Re: porting

[Armando Di Cianno]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2005-10-05 00:01:13 -0400 Chuck Robey <chuckr@chuckr.org> wrote:
> Neither work out of the box on the Zaurus.  The notes included with 
> libffi 
> shows just what sort of fine guy the writer of libffi is, because 
> it's all 
> out there, even test code.  If I can't write that stuff, I don't 
> deserve the 
> great challenge.  On the other hand, there's nearly no info on 
> libffcall. 
> I'm not saying it's going to be impossible, but it sure as heck is 
> going to 
> be a great deal more difficult to do, so the question is: is it 
> really worth 
> it, to go for libffcall, or could libffi do the job (once I get it 
> ported)??

WRT GNUstep, I've had varying luck with both, possibly leaning toward
the sentiment that ffcall is more stable than libffi (again, wrt
GNUstep).

However, as far as using ffcall or libffi in my own development, I've
found that ffcall generally has better documentation.  I'd start with
"man 3 [avcall | vacall | trampoline | callback ]" depending on what
sort of ffi you need to do.

If you ned to extend ffcall or libffi, rather than program with it ...
I haven't poked around in the libffi sources much, but ffcall is
fairly straightforward -- if you know another arch better than i386 I
suggest looking at all the files for that arch as examples (falling
back to i386, if you need to -- or if you know that best, go for it).

Good luck -- your project sounds neat.

__Armando Di Cianno

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux)
Comment: Using the GPG bundle for GNUMail

iD8DBQFDQ/IzwgiTPLI9xhcRArONAJ0ZRfA5e8hNWzXStRYm6Y2MyPgzQQCePMyd
hoSmhawoovL2wx4izmAt14E=
=0w+o
-----END PGP SIGNATURE-----