Re: [Sablevm-developer] Short release status - almost there...

[Etienne G. <gag...@uq...>]

Chris Pickett wrote:
>> 2. Updated http://devel.sablevm.org/docs/INSTALL.txt document, which
>> serves as both: release notes and installation instruction, and put it
>> into sablevm/staging as INSTALL-DEVEL text file (made it included in
>> the "dist" tarball - should be removed on migration to trunk!).
> 
> 
> Seems like common practice would be to put a single INSTALL file in the 
> top level of sablevm.

I agree with the INSTALL file.

Another thing:  I do really think that "./configure ; make ; make install"
should work out-of-the-box for sablevm-x.y.z.tar.gz and for
sablevm-classpath-x.y.z.tar.gz.  Currently, it is broken for
sablevm-classpath (as you need to pass specific configure options to get
a sablevm usable build).  Assume that the typical user WILL NOT read the
README file nor the INSTALL files and will simply go ahead and type the
standard commands above.  [Alternatively, you could make sure that
"./configure" fails for sablevm-classpath, and issues a message inviting
the user to read the README and INSTALL files...]

The worst situation is if a user does the standard commands, gets no build
error message, yet gets "could not start vm" when trying to run HelloWorld.

What do you think?

Etienne

-- 
Etienne M. Gagnon, Ph.D.             http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/