[Vm-dev] VM packaging for Cog transition
andreas.raab at gmx.de
Tue Nov 9 18:20:42 UTC 2010
On 11/9/2010 10:10 AM, K. K. Subramaniam wrote:
> Bert's reply is ingenious ;-). Generated files are intermediate files, not true
> source files. True "sources" are actually Slang code in VMMaker image and these
> should be in version control.
The generated files are true source files. If you've ever had the need
to ensure that you're building the same VMs across various platforms
you'll quickly find that you're moving generated files around, not images.
> When bootstrapping VM on a new platform, a sub-set of these intermediate files
> along with hand-coded source files are compiled generate a proto-vm. The proto-
> vm runs VMMaker image to translate all Slang code into C so that the regular
> VM and plugins can now be built and the proto-vm can be discarded.
> The VMMaker image is a critical part of bootstrap and should be put under
> version control.
No and no. When bootstrapping a new VM on a new platform you move the
generated files and start from those. The VMMaker image is an
afterthought, only used for generation of the sources and not involved
in the bootstrap of a new platform at all.
More information about the Vm-dev