Re: [Sablevm-developer] New SableVM build script

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

Hi Bruno,

As you probably saw, I just wasted a bit of time making a build-dev 
script for SableVM.

However, some things I did aren't done in your script.  It would be nice 
if you made a version of your script for developers, such that it:

1) recognized the directory structure in the CVS (sablevm, 
sablepath-classes, and sablepath-libs).

2) ran the necessary autoconf stuff

3) ran etags -R .... this might require some fiddling, I couldn't get it 
to work on my Sable account

4) ran make indent

5) checked for an environment variable specifying where to put the dev. 
build, and if not found, asked for one, but would not put it in 
/usr/local ... presumably most people do not want this if developers.

6) deleted the previous installation directory.

7) didn't require a fresh CVS checkout for a new build (problem with my 
script).

I would do this, but you clearly have a much better understanding of how 
scripts work . . .

Cheers,
Chris

Bruno Dufour wrote:

>Hi,
>
>	I am contributing a new (bash) build script for SableVM which is meant to 
>replace both build & build-many. It has a lot of new features, including 
>checking the exit status of all executed commands (so it does not go on if 
>one of them fails). It is implemented using a lot of functions, so as to make 
>it easy to change a particular phase. It is now also easy to add new SableVM 
>configurations. 
>
>Using the script:
>
>'build' becomes 'build-sablevm' and 'build-many' becomes 'build-sablevm 
>--vms=all'. You can also type something like build-sablevm 
>--vms=inlined,direct,switch.
>
>Also, there is no longer a dependency on the user not including the trailing 
>slash after the installation path. It is stripped off if included. Try 
>running the script with --help to learn more about how to use it.
>
>Let me know if you have any specific request / suggestion.
>
>  
>