[squeak-dev] managing the transition to 64-bit

Levente Uzonyi leves at caesar.elte.hu
Mon Dec 12 18:55:54 UTC 2016

Do you mean that you want to make a single executable to run both 32-bit 
and 64-bit images?
If so, you can make a script which reads the image version from the header 
and runs it with the corresponding VM.
But I don't see why you would want to do that. :)


On Mon, 12 Dec 2016, Chris Muller wrote:

> I'm ready to make a push to migrate all my stuff to 64-bit, so this
> means I need the ability to run either a 32-bit VM or a 64-bit VM, at
> least for now.  Unfortunately, it appears each uses the same the VM
> file directory structure, and so whichever one is installed last
> stomps out the other.
> Eliot, you have unique names for VM versions, have you considered
> inserting something to uniquefy the names to support co-existence of
> 32 and 64-bit of the same VM version?  Or, does anyone have any best
> practices to allow the co-existence of 32-bit with 64-bit VM?
> I'm not talking about the problem with the names of the executables
> (scripts) all being "squeak".  I've already been renaming the shell
> scripts from "squeak" to "cog" or "spur".  Now the problem between 32
> and 64-bit is the "lib" directory they refer to -- they share the
> exact same name.
> I still have a lot of 32-bit images around.  Does anyone have any
> pointers on how best to manage both a 32-bit and 64-bit?

More information about the Squeak-dev mailing list