Thread: [Sablevm-developer] New SableVM build script
Brought to you by:
egagnon
Menu
▾
▴
sablevm-developer
|
From: Bruno D. <bru...@ma...> - 2003-02-06 04:19:13
Attachments:
build-sablevm
|
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. -- Bruno Dufour Sable Research Group McGill University, Montreal, Canada bru...@ma... |
|
From: Chris P. <chr...@ma...> - 2003-02-20 00:50:48
|
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. > > > |
|
From: Prof. E. M. G. <eti...@uq...> - 2003-02-20 01:18:54
|
On Wed, Feb 19, 2003 at 07:50:59PM -0500, Chris Pickett wrote: > 3) ran etags -R .... this might require some fiddling, I couldn't get it > to work on my Sable account Petition your system's administrator to: $ apt-get exuberant-ctags This will solve your problem. The plain ctags is supported by "make tags", I think, but you get so much more using exuberant-ctags... Also, I'm trying to finish a small 1.0.6 release. We'll put the newer scripts in another release. Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ |
|
From: Prof. E. M. G. <eti...@uq...> - 2003-02-20 01:24:14
|
On Wed, Feb 19, 2003 at 08:13:33PM -0500, Prof. Etienne M. Gagnon wrote: > Petition your system's administrator to: > $ apt-get exuberant-ctags I meant: $ apt-get install exuberant-ctags of course. Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/ |
|
From: Chris P. <chr...@ma...> - 2003-02-20 01:01:46
|
Bruno, by the way, it would also be nice if all of the configure options could be specified from your script, e.g. --with_gc, --with_obj_layout, etc, because there's more than just 6 combinations. I think nobody used your script because it isn't useful for developers. I just got your message about the "oops" email. It had a time of 2:49 p.m. (which doesn't make sense). 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. > > > |
|
From: Bruno D. <bru...@ma...> - 2003-02-20 01:09:16
|
Ok, I'll try to include that. It should be easy enough to do. Thanks for your feedback. BTW, my system clock displays the right time and date! Maybe it's internally set to UTC and my e-mail client does not like that... Thanks for pointing it out. Cheers, Bruno On Thursday 20 February 2003 01:01 am, Chris Pickett wrote: > Bruno, by the way, it would also be nice if all of the configure options > could be specified from your script, e.g. --with_gc, --with_obj_layout, > etc, because there's more than just 6 combinations. > > I think nobody used your script because it isn't useful for developers. > I just got your message about the "oops" email. It had a time of 2:49 > p.m. (which doesn't make sense). > > 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. > > ------------------------------------------------------- > This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. > The most comprehensive and flexible code editor you can use. > Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. > www.slickedit.com/sourceforge > _______________________________________________ > Sablevm-developer mailing list > Sab...@li... > https://lists.sourceforge.net/lists/listinfo/sablevm-developer -- Bruno Dufour Sable Research Group McGill University, Montreal, Canada bru...@ma... |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X