[Vm-dev] VM packaging for Cog transition

Andreas Raab andreas.raab at gmx.de
Tue Nov 9 18:06:54 UTC 2010

On 11/9/2010 2:25 AM, Bert Freudenberg wrote:
> Shouldn't we have a single folder for generated plugins? Also, I always felt that "src" was misleading. So how about this:
> platforms/
> 	Cross/
> 	Unix/
> 	Mac OS/
> 	Win/
> 	iOS/
> generated/
> 	interp/
> 	jit/
> 	stack/
> 	plugins/
> However, one reason to put the generated sources inside the platform folders was because often the platform code lagged behind, and only the single maintainer could fix it. A better solution to that would be opening up VM development. As I mentioned before I'd like us to move to a DCVS. If we intend to change the repository structure this would be an excellent time.

I don't think these issues are related at all. A particular release will 
still bundle a certain version of the platforms tree with a certain 
version of the generated code. However, there is no requirement for the 
generated code to live inside the platforms directory. To make it one 
notch more complicated, our internal structure for VM building actually 
puts the various toolchains side-by-side with platforms and 
src/generated, i.e.,

cygwinbuild/  "<- Windows Cygwin build"
macbuild/     "<- Mac X-Code build"
mgwbuild/     "<- Windows MingW build"
mscbuild/     "<- Windows Visual C++ build"
unixbuild/    "<- Unix gcc build"

This has some advantages for us since we can check in and build VMs from 
the same (checked-in) src/ and platforms/ tree in the various 
environments, but I'm not sure we need this for the Squeak VM in general.

   - Andreas

More information about the Vm-dev mailing list