[Vm-dev] Separating launcher from VM binaries

Ben Coman btc at openinworld.com
Thu Apr 18 08:41:03 UTC 2019

On Wed, 17 Apr 2019 at 00:04, K K Subbu <kksubbu.ml at gmail.com> wrote:

> Hi,
> In working with Squeak images of different formats and word sizes, I
> find myself struggling with a bunch of scripts - run, squeak, squeak64,
> cog, cog64, spur, spur64 etc and having to update the run script
> whenever a new format comes out. There should be simpler way .....
> It would be nice to separate the main programs - launcher(squeak) and
> ckformat - from the VMs that read specific image formats.
> VMs could be generated with base format built into the name or path e.g.
> lib/$VER/$BASE/ostvm or lib/$BASE/$VER/ostvm
> The main launcher (squeak) will probe and launch a matching VM with
> something like:
>     lib/$VER/$(ckformat $IMAGE)/$VMNAME $ARG
> without having to find out the exact format number. This will enable
> multiple format VMs to co-exist in a machine without having to change
> PATH settings etc.

PharoLauncher does this... https://github.com/pharo-project/pharo-launcher
Maybe you could reuse some of it.  Review might start with:
* PhLVirtualMachineTest
* PhLVirtualMachineManagerTest
* PhLVirtualMachineManagerFunctionalTest

cheers -ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20190418/3e297c36/attachment.html>

More information about the Vm-dev mailing list