[squeak-dev] new VM directory structure for 5.3
Christoph.Thiede at student.hpi.uni-potsdam.de
Sat Jan 11 13:08:53 UTC 2020
On Windows, I put the VM and related files (libraries, release notes, ...) into %ProgramFiles%. This has the advantage of a persistent file path that does not change and it's easy to find via OpenWith, so I can associate the VM with the .image filetype. It may be even more useful to put the VM into %LocalAppData% to get rid of UAC problems (the crash.dmp file is written into the same directory). From my point of view, an installer & updater for the VM would not be bad ...
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Herbert König <herbertkoenig at gmx.net>
Gesendet: Samstag, 11. Januar 2020 12:49:21
An: squeak-dev at lists.squeakfoundation.org
Betreff: Re: [squeak-dev] new VM directory structure for 5.3
In Windows you just copy one folder to the next machine and everything
works. Which btw is an advantage Squeak has over Windows software that
I had hoped that Linux Squeak would make one step into that direction,
but there seem to be arguments against it (I'm not qualified to argue
Am 11.01.2020 um 06:55 schrieb K K Subbu:
> On 11/01/20 3:53 AM, Chris Muller wrote:
>> This simplification allows easy co-existence of 32-bit with 64-bit
>> versions of the same VM.
> If the bin directory is created with <os>-<isa>-<optional-variant>/
> then it would be simpler and easier to ship and share multiplatform
> code (e.g. shared mounts). Is it too late to make the change?
>> The SqueakV50.sources file must be present in at least one of those
>> two directories.
> *.sources does not have any arch-specific code. It would be better to
> specify the shared directory only but be lenient and look in bin*
> directory if it is missing there.
> Regards .. Subbu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev