> -----Original Message-----
> From: John M McIntosh [mailto:johnmci at smalltalkconsulting.com]
> >
> >I would recommend that we Consolidate all of the platform makers into 
> >one version of VMMaker, doing the appropriate things with 
> >'intplugins'.  The default ought to be with no intplugins, I would 
> >think.
> >
> >Rob
> 
> I think we can do this, it's a bit more work for initial mac setup 
> because you must hunt for all the files. Ya someday we *might* be 
> able to build a pb project in VMMaker, we'll see.

So, what's different about startup between win32 and mac?  Is it that
platforms file copy is turned off, requiring you to hand edit the Makefile?

You've reminded me that there is another difference between VMMaker 3.1.3
and 3.2.5.  First, 3.2.5 puts internal plugins into 'vm/intplugins', by
default.  Second, 3.2.5 does not copy the platform files.  Win32 doesn't
want to do either at this point.  Does the mac?

In win32, I want the file copy to occur for now.  Then there is no mucking
about with the Makefile targets.  Ya someday we *,might* generate Makefile
targets, based on plugin configuration.  :)

> Also is that win VM really support long file names and 64 bit large 
> files (or whatever limits Bill gives you?)

Andreas, will have to answer this one; I'm just the indentured servant.  I
do know that it compiles with all of the most recent changes, both
changesets and 'Cross' platform files.

Rob