Separating launcher from VM binaries

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Separating launcher from VM binaries

K K Subbu
 
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.

Regards .. Subbu
Reply | Threaded
Open this post in threaded view
|

Re: Separating launcher from VM binaries

Edgar De Cleene
 
A poor man solution.
Export all relevant as .obj using the attached.
The serialized objects is compatible between all Squeak and if use same
clases in both, with Cuis also.
My working .obj of squeakros.org have inside 6000+ "pages" and works on all

My 2 pesos :=)


On 16/04/2019, 13:04, "K K Subbu" <[hidden email]> 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.

Regards .. Subbu



ObjectCompatibleENH.1.cs (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Separating launcher from VM binaries

Ben Coman
In reply to this post by K K Subbu
 
On Wed, 17 Apr 2019 at 00:04, K K Subbu <[hidden email]> 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.

Maybe you could reuse some of it.  Review might start with:
* PhLVirtualMachineTest
* PhLVirtualMachineManagerTest
* PhLVirtualMachineManagerFunctionalTest

cheers -ben