On Feb 13, 2007, at 1:28 PM, Aldo Calpini wrote:
whoa there!
furthermore, the Configure process uses $^O here and there, and this
should eventually be replaced by an --arch=something parameter to
Configure.pl (which defaults to $^O, of course).
my parrot does indeed run some of the examples/pasm files. I tried
hello.pasm, fact.pasm, xml_parser.pasm, they all run just fine.
now, from what I understand looking at the Makefile, this parrot
should be used to generate a lot of .pbc files that constitute the
"core" Parrot library. this is going to be a real pain, because while
it's true that I can run parrot on the PDA, all the directory
structure (eg. runtime/parrot/library) is not there at all.
so I'm really puzzled about what to do next. is this parrot.exe alone
worth something (except for running .pasm files, that is)? should I
transfer the whole parrot directory to the PDA and build the library
there, by hand?
I would appreciate any feedback :-)
cheers,
Aldo
You should be able to run most pir files and pbc files too, since the
pbc files are platform independent. It'd help to have then generated
on a platform with the same endian for speed, but not required(portable
byte code). You can sort of pick and choose which libraries if you're
feeling adventurous, and which headers. They're often used in other
files to run. You won't need all the .h files since they're for
linking with libparrot, so just the stuff with runtime. You may even
be able to get tcl running on your pda.
