Re: [Chicken-users] Chicken 2.3 - How to compile statically with eggs?

[felix winkelmann]

On 4/27/06, Samuel Jenkins <address@hidden> wrote:
> Hi all!
>
> First of all... I've ported the Chicken runtime to the handheld Linux
> console Gamepark Holdings GP2X-F100. But my cross-compiler (gcc 4.0.2) has a
> different libc than the GP2X firmware, so to get my executables to run in
> the console I have to link statically.

Hey, cool!

> I want to be able wo write a program, test it thoroughly on linux i386 using
> 'csi' and then cross compile it statically to the GP2X, without having to
> modify it. But I am clueless about how to compile statically a Chicken
> program with their required eggs.
>
> I've tried to run a 'chicken -extension' on all required modules, then a
> 'chicken' on the main program, that has the corresponding
> '(require-extension)' directives on top, and then running 'csc -static' on
> the resulting .c files. And it was unsucessful, the program shows an error
> if the required eggs are not present in the same directory.

Yes, this process of statically compiling eggs is somewhat tricky
and not always intuitive. I have written a few tips about that topic
here:

http://galinha.ucpel.tche.br/coop?page=Linking%20eggs%20statically

and

http://galinha.ucpel.tche.br/coop?page=Deploying%20Linux%20binaries

> I've tried during two days of getting this static egg compilation working
> but now I'm really clueless and frustrated. What can I do? Should I have to
> switch to using 'dirty' (include)'s ?

What eggs exactly do you need?


cheers,
felix