Re: [Chicken-users] cross compilation, emedded platform

[Dan]

You will not believe me, but this platform has no
files, no stdio, no network, just a UART, some LED's,
and one TDM port. So, yes, I want to build as little
as possible, because every file compiled yields
gazillions of errors that need to be addressed.

In the meanwhile, I've realized that minimally I just
need to build libchicken. C files produced by the host
"chicken" are more or less portable, but require
libchicken.

The only obstacle that remains is that libchicken uses
stat and other file manipulation functions.

And, by the way, CMake is too difficult for this task,
as is pretty much "make" at this point. You have no
ideea how painful libtool, autoconf and automake are
when cross-compiling. I'm having a hard enough time
separating things meant for the host from things meant
for the target. I need to put together a compile.sh
shell script.

-- Dan

--- "Brandon J. Van Every" <address@hidden>
wrote:

> Dan wrote:
> > OK, I'm a little confused in my embedded chicken
> > efforts. I want to build the chicken compiler for
> the
> > target platform and static libraries. I do not
> want
> > shared libraries or csi (there are no .so's or
> stdio
> > on the platform).
> >   
> 
> Do you strongly object to just building everything?
> 
> > What exactly is the make target that I need to
> build ?
> > chicken, csc or what? It seems that csc is just a
> > wrapper for chicken.
> >   
> 
> Sounds like you'll want to spend some time reading
> the manual and also 
> the Makefiles.  csc is a frontend for chicken.  It
> can offer a more 
> convenient interface if it's working properly.  I'm
> not entirely 
> confident that it's working properly for the CMake
> build, but you aren't 
> using that at present anyways.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com