Re: [Sablevm-developer] Priority list

[Chris P. <chr...@ma...>]

>
>compiling sablevm in different ways.
>
>The very serious question is whether my approach of "swiss-army-knife"
>is right (Chris says that Bruno's script is easier to read, so there's
>probably sth. wrong with mine).
>
I wouldn't necessarily listen to me as I don't know enough about scripts 
to write either yours or Bruno's.  I'm sure you guys can work something 
out.  I think the various sablevm builds should not be built into the 
script itself, but only the different options passable to configure (it 
would be nice to see one letter abbreviations though, like SDIGTB for 
switch, direct, inlined, GC, traditional, bidirectional).   Rather, the 
user can invoke the script specifying how many different builds and with 
what options.  If they like, this can go in a secondary script.  The 
main purpose is to simplify the autoconf routine, as well as handling 
CVS and .tar.gz distributions.  I don't know, I'm rambling.

Cheers,
Chris