[Vm-dev] Re: Uploaded squeak-vm 3.11.3
David T. Lewis
lewis at mail.msen.com
Wed Jan 27 00:54:27 UTC 2010
On Tue, Jan 26, 2010 at 12:27:54PM -0800, Bert Freudenberg wrote:
>
> On 26.01.2010, at 12:01, Eliot Miranda wrote:
> >
> > On Tue, Jan 26, 2010 at 11:56 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> >
> > On 26.01.2010, at 11:03, Eliot Miranda wrote:
> >>
> >>
> >> On Tue, Jan 26, 2010 at 9:39 AM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> >>
> >> On 26.01.2010, at 05:31, Jos? L. Redrejo wrote:
> >> >
> >> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497583 I have not ideas
> >> > to argue with this man. In fact, I think he might be totally right.
> >>
> >> Well, there is a source for this of course (in the VMMaker Squeak package). Generating the C code is a manual, interactive process and requires a running Squeak installation. Making that scriptable is possible, but so far nobody has done it AFAIK.
> >>
> >> FYI, Peter von der Ahe did it in the Newspeak project. This isn't entirely relevant because some of this may be Newspeak code, but the source is available from http://newspeaklanguage.org/the-newspeak-programming-language/downloads/ & newspeak-source-2009-10-28.zip
> >>
> >
> > I guess you're referring to NsVmMaker.ns1? That does not seem to be used by the regular build process. I guess it is invoked manually to regenerate the sources.
> >
> > Yes-ish, IIRC from a gnu make makefile.
>
>
> If so, it's not included in the source release. No makefile (or other build-related file) refers to "NsVmMaker".
>
> Thanks anyway :)
>
> - Bert -
>
Got to give Tim Rowledge some credit on this one folks. Given a known
directory structure and a VMMaker configuration file saved from a
VMMakerTool, the script for generating the source code is just this:
(VMMaker forConfigurationFile: 'myConfig.config')
deleteEntireGeneratedTree;
generateEntire.
VMMaker is also designed to be scriptable (i.e. controllable independent
of the VMMakerTool interactive tool). See Tim's class comment for details.
Dave
More information about the Vm-dev
mailing list