Compiling Euphoria 3+ for non-x86 targets
With the change of Euphoria to an open source model, I'm wondering if any
thought is being given to how non-x86 ports are going to be handled within
the source.
Some of you might remember that I ported a (mostly) working version of Eu
2.4 to my Sharp Zaurus clamshell pda, ARM/Xscale/Linux, back when the source
was fully C. I managed to get Eu 2.5 (partly broken) compiled for the Z
using a halfway house method of translate on Linux PC, compile on Zaurus.
This time, I've completed a successful but completely broken compile of
3.0.2, using the 2.4 interpreter on my Z to run the new PD translator (2.4
is missing the '$' shorthand and it was necessary to replace a few instances
of that with 'length()' ) The resulting interpreter segfaults immediately
following the file request message. I'm not too concerned about that as
there is a lot to do in the source. A lot of what needs to be done is, I'm
guessing, going to be just like what I've already done in 2.4. Transferring
all of that to the 3.0.2 source is going to be very tedious.
Is there any way we could keep track of where changes have been made in the
source? Perhaps a formal method for commenting them, like "//change: V3.0.2
[code....] //end change"? This could be quickly searched for using a text
editor, providing it was consistent.
Btw, is anyone else porting to a non-x86 platform? I'd be particularly
interested to hear from any ARM gurus who would be willing to help me with
the ARM asm code. My poor effort (necessary to implement shared lib calling)
worked in 2.4 but refused to do so in 2.5.
Mark
|
Not Categorized, Please Help
|
|
