Re: [Sablevm-developer] Release progress - problems w/ 'make distcheck' of classpath

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

Etienne Gagnon wrote:

> Chris Pickett wrote:
> 
>>> But I am sure staging shouldn't claim to be just "1.0.9" or any other
>>> release. I wanted to put "staging" name initialy, but I guess
>>> "1.0.9+staging" or (hopefuly soon) "1.1.0+staging" should at least give
>>> some more informations if we ask a user to do 'sablevm -V' for us.
>>

> I think that sablevm staging should report:
> - SableVM version "Staging Sapshot"  (optionally with a UTC date/time...
>   but that would be a hassle as what we want is the svn revision checkin
>   UTC date/time, not the "build or configure" date/time).  Be warned:
>   svn log reports "local" date/time.

I don't think time is as meaningful as just revision number.

$ svn info | grep "Last Changed Rev:" | cut -d' ' -f4

is a useful pipeline :)  However, what's the best place to do the find 
and replace?  In configure.ac?  That way I think the number would make 
it into a tarball.

> - it should also report about the status of "--disable-no-reorder-block"
>   and all other "configure" options that were explicitly or implicitly
>   selected.

What if the binary / directory names simply reflect all non-default 
configure options, aside from the switch/direct/inlined choice?

(so, sablevm-staging-rXXXX-inlined is the default)

Otherwise, I'm not sure what you mean by "report".  Where do you want 
this reported?

$ cat config.log | grep '^#define _SABLEVM'

seems pretty good -- I currently get the following:

#define _SABLEVM_BIDIRECTIONAL_OBJECT_LAYOUT 1
#define _SABLEVM_COPY_GC 1
#define _SABLEVM_PACKAGE_NAME "sablevm"
#define _SABLEVM_PACKAGE_VERSION "1.0.9" <-- becomes "staging-rXXXX"
#define _SABLEVM_SWITCH_THREADED_INTERPRETER 1

Cheers,
Chris