[Vm-dev] VM packaging for Cog transition

K. K. Subramaniam kksubbu.ml at gmail.com
Tue Nov 9 16:56:07 UTC 2010


On Tuesday 09 Nov 2010 3:55:53 pm Bert Freudenberg wrote:
> Shouldn't we have a single folder for generated plugins?
IMHO, plugins should be capable of being built anywhere, even outside the VM 
sources. Plugins, by definition, use arch-specific or os-specific features and 
the 'upper half' could be squirted into platform directory as necessary.

> Also, I always
> felt that "src" was misleading. So how about this:
> 
> platforms/
> 	Cross/
> 	Unix/
> 	Mac OS/
> 	Win/
> 	iOS/
I prefer <arch>/<platform>/<os> structure (e.g. x86/pc/Win32, WinCE, Win64, 
linux, Mac OS, arm/davinci/linux,..). It is much easier to re-use code and 
development tools this way.

> generated/
> 	interp/
> 	jit/
> 	stack/
> 	plugins/
I would vote to skip generated/ and Cross/ directories and leave all these file 
at top level. Apart from C code, there could also be auto-generated 
configuration files, Makefiles etc. Why treat C code specially?

> 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.
+1

> 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.
A distributed version manager like git would be useful only for hand-coded 
files. What about blobs like images, changesets and sources?

Subbu


More information about the Vm-dev mailing list