chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: john
Subject: Re: [Chicken-users] Chicken 2.3 - How to compile statically with eggs?
Date: Thu, 27 Apr 2006 21:13:58 +0100

I have not used a GP2X but on the Sharp Zaurus I have encountered similar problems where cross compiler toolchain supported glibc 2.3 but the target device only had glibc 2.2. With the Zaurus you can flash a new ROM to use a distribution which has glibc 2.3 (openzaurus.org). You can then build Chicken with scratchbox (scratchbox.org). I am actually using a ROM which is based on glibc 2.2 (pdaxrom.org) so not using scratchbox. I built it using the supplied cross compiler. I also was able to build Chicken with a cross compiler available for Mac OS X. Both builds allowed dynamically loadable code. If you run the interpreter you should see it lists "dload". Then it is a question of building various eggs which can be a bit tricky in a cross compilation environment so I installed gcc on my Zaurus and just built them in the normal way.

I actually was thinking of getting a GP2X as it looks a cool way to learn some games programming and Chicken and SDL seems to go together really well.

John.

On 27/04/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.

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.

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 ?

Thanks in advance,
   Sam 'XhyldazhK' Jenkins.

--
Analog-/ISDN-Nutzer sparen mit GMX SmartSurfer bis zu 70%!
Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer


_______________________________________________
Chicken-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/chicken-users


reply via email to

[Prev in Thread] Current Thread [Next in Thread]