Hello Parrot, For this year's GSoC I'm working on making Parrot run on RTEMS[1]. This requires cross-compilation support[2], and the work is divided into two tickets.
First I'll be tackling TT #1516[3] that will allow Parrot to be built in a directory that is not the source directory. The goal is to be able to run the following in a folder containing the source: mkdir build cd build perl ../Configure.pl make This is a rather mundane example, but it would allow us to have multiple copies of Parrot (perhaps configured differently) all running from the same checkout of code. Regular in-directory building will not be effected. Secondly TT #1195[4] will be focused on making Configure.pl cross-compilation safe. Currently the Configure.pl script assumes that the Parrot we are building will run our current system, which is not the case for cross-compilation. For example, if I'm running x86 and targeting a sparc architecture, the parrot that I build won't be able to run on my own machine and the bootstrapping steps will fail. So I will separate the Makefile $(PARROT) into $(BUILD_PARROT) and $(HOST_PARROT) so $(HOST_PARROT) can be provided at configure time. Again, for normal builds (where build system = target system) nothing will change. Any experts in these areas - I'm more than eager to hear your input. I'll keep my work on TT #1516 on the branch[5] and merge once everything is tested and clean. If any of this is unclear feel free to email me back for clarification. bubaflub [1] http://www.rtems.org [2] http://en.wikipedia.org/wiki/Cross_compilation [3] http://trac.parrot.org/parrot/ticket/1516 [4] http://trac.parrot.org/parrot/ticket/1195 [5] https://svn.parrot.org/parrot/branches/tt1516_builddir_option/ _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
