It would seem that its probably best we take some time and try to spec out, test, and the publish the steps to follow since I've been interested in a port like this as well.
Can we use the steps followed to port PFC to the MacOS hardware platform when it was non-Intel? Should be be looking at a cross-compile approach using the i386 host (Linux) and the SheevaPlug developer tools? How can we condense down the FPC libraries and what linking strategy should we use? (static) Just a few questions that I have on my mind looking at this. Prince On Tue, Apr 14, 2009 at 4:21 PM, Henry Vermaak <henry.verm...@gmail.com>wrote: > 2009/4/14 Florian Klaempfl <flor...@freepascal.org>: > > Henry Vermaak schrieb: > >> first you need to get fpc to work, which means that you might have to > >> build an eabi compiler, since most distros (even debian) now use eabi > >> (the default arm fpc is oabi). > > > > Well, not really. Debian stable is still oabi. > > hmm, according to this: http://www.debian.org/ports/arm/ the oabi is > deprecated... > > henry > _______________________________________________ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/mailman/listinfo/fpc-pascal >
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
