On Wed, 21 Apr 2010, Will Coleda wrote:
> I was going to open a ticket on tools/dev/mk_native_pbc, but will hit
> the list first, as this could be several tickets; I'll post a laundry
> list here and get some feedback before opening tickets.
>
>
>
> - is written in sh - We should consider porting it to perl even if it
> will only ever run on platforms with sh. (one less language in our
> build kit.)
>
> - needs documentation - when to run it? why to run it? plans about
> obsoleting it?
I would stop right here. Before investing time in it, it would help to
have a larger plan.
If you want to proceed anyway, then I think mk_native_pbc ought to
make the native pbcs for the current configuration only, and that's it.
The current default behavior of destroying your existing configuration
is mad. It shouldn't try to reconfigure and rebuild parrot, since it's
(a) difficult to get that right in a general way, and (b) potentially very
time-consuming. Reconfiguring and rebuilding parrot is a separate job,
and could, perhaps, be done by a different higher-level tool, if at all.
Of course that tool might then invoke mk_native_pbc, as appropriate.
--
Andy Dougherty [email protected]
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
