[Vm-dev] Adding VectorEnginePlugin to standard VM distributions for Cuis/Squeak

[David T. Lewis]

On Wed, Jul 21, 2021 at 09:22:38PM -0400, David T. Lewis wrote:
>  
> On Wed, Jul 21, 2021 at 08:28:15PM -0400, David T. Lewis wrote:
> >  
> > On Wed, Jul 21, 2021 at 12:09:35PM -0700, Eliot Miranda wrote:
> > > On Tue, Jul 20, 2021 at 5:48 PM David T. Lewis <lewis at mail.msen.com> wrote:
> > > 
> > > > Are there any preferences or recommendations as to how to best handle this?
> > > > I have been tracking the VectorEnginePlugin for some time and I'm willing
> > > > to do any administrative things that may be needed, including checking in
> > > > generated sources and/or possibly setting up and maintaining a Monticello
> > > > mirror of the upstream repository (e.g. a project on squeaksource) if
> > > > that is preferred.
> > > >
> > > 
> > > An upstream Monticello mirror would be most helpful.  We have a tiny script
> > > for generating correct histories in exports to Monticello from Tonel
> > > repositories if it is of help.  I will fold the VectorEnginePlugin into the
> > > standard builds within the next few days (not today, I need some downtime).
> > > 
> > 
> > I have been keeping MCZ checkpoints of Juan's git commits on my own PC,
> > because that was an easy way for me to keep track of the VectorEngine
> > development and test it on VMMaker[.oscog]. This has been remarkably
> > painless to do, but maintaining it is a manual process so I don't know
> > if it is a good long term approach.
> > 
> > I would be happier to be able to have our VMMaker images point directly to
> > Juan's upstream github repository, but I don't understand our Squeak/git
> > tooling well enough to make it happen.
> > 
> > I can push the MCZ files up to a new project on squeaksource.com as an
> > interim(?) step. I'll reply back when that is done.
> > 
> 
> I set up a mirror at http://www.squeaksource.com/VectorEnginePlugin.
> 
> Eliot, you and I are admins. Juan, I don't have see a squeaksource.com
> user ID for you so I guess you will have to trust us.
> 
> The commits are up to date with the upstream Cuis repo but will need
> manual updates as Juan makes future commits. I will make sure that this
> gets done, and I'll look for help on the Squeak/VMMaker side to see if
> we can remove squeaksource.com as the "middle man".
> 

I pushed the generated source for VectorEnginePlugin as of commit 06090c3
to the squeakvm.org SVN repository for interpreter VM (Cuis V3 images),
and also updated VMMaker (old version for interpreter VM) to include
VectorEnginePlugin in the code generation. Build script 'mkvm' is attached
for interested Linux hackers.

Next step - Eliot and/or I will update opensmalltalk-vm to include
VectorEnginePlugin in the high performance standard VMs.

Dave

-------------- next part --------------
#!/bin/sh
#
# Mon Jun 13 22:45:41 EDT 2016 dtl
#
# Compile an interpreter VM from the most recent sources in squeakvm.org repository
#
# Prerequisites:
#   CMake build system https://cmake.org/download/
#    (note CMake 3.0.2 is known to work, newer versions assumed to work also)
#   Subversion version control system, available through Linux distributions
#   C compiler and development libraries (32-bit compatibility not required)

REPO=http://squeakvm.org/svn/squeak/trunk

# Get or update the latest platforms sources and generated VMMaker sources
if test -d platforms
then
  svn update platforms
  svn update src
else
  svn co $REPO/platforms
  svn co $REPO/src
fi

if ! test -d build
then
  mkdir build
fi

cd build
cp ../platforms/unix/cmake/Makefile.example Makefile
make clean; make

# Notes: Installation requires root privileges. Installation may conflict with
# previously installed VMs (e.g. Cog, Spur).

if test $?
then
  echo VM build complete
  echo To install the VM as /usr/local/bin/squeak do \"\$ sudo make install\" in the ./build directory
  # sudo make install
fi