Hi All,
I'm trying ot update the VMMaker image build scripts. I've got as far as downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!).
How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress?
I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st
where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_ best, Eliot
Hi All,
ok, this is a bit of a disaster. The invocation is now:
Squeak.app/Contents/MacOS/Squeak trunk6-64.image UpdateSqueakTrunkImage.st
Why was it changed?
And the result:
1. the update fails with a merge conflict in the release builder between: SystemVersion newVersion: 'Squeak6.0' and SystemVersion newVersion: 'Squeak6.1alpha'
2. a Note that says 'Cannot start a second instance of Squeak with the image "UpdateSqueakTrunkImage.st" because the VM is configured as singleton application.' becauser somewhere something is generating a DropFileEvent for the UpdateSqueakTrunkImage.st file. The system shouldn't be both executing the script argument and generating a drop file event for it.
The effective result is that I can't automate building a VMMaker image as I was once able to. :-(
On Thu, Jul 21, 2022 at 6:23 PM Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
I'm trying ot update the VMMaker image build scripts. I've got as faras downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!).
How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress?
I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st
where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_ best, Eliot
Hi Eliot --
1. the update fails with a merge conflict in the release builder between: [...]
If you want to prepare a VMMaker Trunk image, you would use a regular Trunk image, not a release image. I think. So, why aren't you using a recent 6.1alpha image? -> http://files.squeak.org/6.1alpha/Squeak6.1alpha-22134-64bit/
Best, Marcel Am 22.07.2022 05:06:27 schrieb Eliot Miranda eliot.miranda@gmail.com: Hi All,
ok, this is a bit of a disaster. The invocation is now:
Squeak.app/Contents/MacOS/Squeak trunk6-64.image UpdateSqueakTrunkImage.st
Why was it changed?
And the result:
1. the update fails with a merge conflict in the release builder between: SystemVersion newVersion: 'Squeak6.0' and SystemVersion newVersion: 'Squeak6.1alpha'
2. a Note that says 'Cannot start a second instance of Squeak with the image "UpdateSqueakTrunkImage.st" because the VM is configured as singleton application.' becauser somewhere something is generating a DropFileEvent for the UpdateSqueakTrunkImage.st file. The system shouldn't be both executing the script argument and generating a drop file event for it.
The effective result is that I can't automate building a VMMaker image as I was once able to. :-(
On Thu, Jul 21, 2022 at 6:23 PM Eliot Miranda <eliot.miranda@gmail.com [mailto:eliot.miranda@gmail.com]> wrote:
Hi All,
I'm trying ot update the VMMaker image build scripts. I've got as far as downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!).
How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress?
I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st
where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_
best, Eliot
--
_,,,^..^,,,_
best, Eliot
On Jul 22, 2022, at 3:13 AM, Marcel Taeumel marcel.taeumel@hpi.de wrote:
Hi Eliot --
- the update fails with a merge conflict in the release builder between: [...]
If you want to prepare a VMMaker Trunk image, you would use a regular Trunk image, not a release image. I think. So, why aren't you using a recent 6.1alpha image? -> http://files.squeak.org/6.1alpha/Squeak6.1alpha-22134-64bit/
OK, I’ll try that. Thanx!!
Best, Marcel
Am 22.07.2022 05:06:27 schrieb Eliot Miranda eliot.miranda@gmail.com:
Hi All,
ok, this is a bit of a disaster. The invocation is now:Squeak.app/Contents/MacOS/Squeak trunk6-64.image UpdateSqueakTrunkImage.st
Why was it changed?
And the result:
- the update fails with a merge conflict in the release builder between: SystemVersion newVersion: 'Squeak6.0'
and SystemVersion newVersion: 'Squeak6.1alpha'
- a Note that says 'Cannot start a second instance of Squeak
with the image "UpdateSqueakTrunkImage.st" because the VM is configured as singleton application.' becauser somewhere something is generating a DropFileEvent for the UpdateSqueakTrunkImage.st file. The system shouldn't be both executing the script argument and generating a drop file event for it.
The effective result is that I can't automate building a VMMaker image as I was once able to. :-(
On Thu, Jul 21, 2022 at 6:23 PM Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
I'm trying ot update the VMMaker image build scripts. I've got as far as downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!).How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress?
I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st
where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_ best, Eliot
-- _,,,^..^,,,_ best, Eliot
On Fri, Jul 22, 2022 at 07:38:07AM -0700, Eliot Miranda wrote:
On Jul 22, 2022, at 3:13 AM, Marcel Taeumel marcel.taeumel@hpi.de wrote:
??? Hi Eliot --
- the update fails with a merge conflict in the release builder between: [...]
If you want to prepare a VMMaker Trunk image, you would use a regular Trunk image, not a release image. I think. So, why aren't you using a recent 6.1alpha image? -> http://files.squeak.org/6.1alpha/Squeak6.1alpha-22134-64bit/
OK, I???ll try that. Thanx!!
This will probably work with the 6.0 release image:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image UpdateSqueakTrunkImage.st --doit 'Project current addDeferredUIMessage: [PreferenceWizardMorph allInstances do: [:e | e delete]]'
Or maybe just add "PreferenceWizardMorph allInstances do: [:e | e delete]." as the first line of the script.
Dave
Hi Dave,
On Jul 22, 2022, at 7:53 AM, David T. Lewis lewis@mail.msen.com wrote:
On Fri, Jul 22, 2022 at 07:38:07AM -0700, Eliot Miranda wrote:
On Jul 22, 2022, at 3:13 AM, Marcel Taeumel marcel.taeumel@hpi.de wrote:
??? Hi Eliot --
- the update fails with a merge conflict in the release builder between: [...]
If you want to prepare a VMMaker Trunk image, you would use a regular Trunk image, not a release image. I think. So, why aren't you using a recent 6.1alpha image? -> http://files.squeak.org/6.1alpha/Squeak6.1alpha-22134-64bit/
OK, I???ll try that. Thanx!!
This will probably work with the 6.0 release image:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image UpdateSqueakTrunkImage.st --doit 'Project current addDeferredUIMessage: [PreferenceWizardMorph allInstances do: [:e | e delete]]'
Or maybe just add "PreferenceWizardMorph allInstances do: [:e | e delete]." as the first line of the script.
Given that there seems to be a drop event generated somewhere that may cause the script to be launched again later, is there a way of asking if the script is tuning in the context of DoItFirst? Then the first line would be
self isRunningAsDoItFirst ifTrue: [^self]. “do stuff second time around when the system is headful”
Dave
_,,,^..^,,,_ (phone)
On Fri, Jul 22, 2022 at 08:06:19AM -0700, Eliot Miranda wrote:
Hi Dave,
On Jul 22, 2022, at 7:53 AM, David T. Lewis lewis@mail.msen.com wrote:
???On Fri, Jul 22, 2022 at 07:38:07AM -0700, Eliot Miranda wrote:
On Jul 22, 2022, at 3:13 AM, Marcel Taeumel marcel.taeumel@hpi.de wrote:
??? Hi Eliot --
- the update fails with a merge conflict in the release builder between: [...]
If you want to prepare a VMMaker Trunk image, you would use a regular Trunk image, not a release image. I think. So, why aren't you using a recent 6.1alpha image? -> http://files.squeak.org/6.1alpha/Squeak6.1alpha-22134-64bit/
OK, I???ll try that. Thanx!!
This will probably work with the 6.0 release image:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image UpdateSqueakTrunkImage.st --doit 'Project current addDeferredUIMessage: [PreferenceWizardMorph allInstances do: [:e | e delete]]'
Or maybe just add "PreferenceWizardMorph allInstances do: [:e | e delete]." as the first line of the script.
Given that there seems to be a drop event generated somewhere that may cause the script to be launched again later, is there a way of asking if the script is tuning in the context of DoItFirst? Then the first line would be
self isRunningAsDoItFirst ifTrue: [^self]. ???do stuff second time around when the system is headful???
It's best to do only very minimal things in any of the DoItFirst options. These run at the very earliest possible time in the startup list processing, so many things have not yet been initialized at that point. For doing anything non-trivial, you will want to use the normal start up script loader (as you already are doing for the VMMaker scripts).
The --doit option (and similar) is just a hook for running a snippet prior to startup processing, which is helpful if you have a broken image that you need to repair before it goes through the full startup list. Or you can use it to evaluate some expressions prior to running your actual script file.
Dave
Hi Dave,
On Fri, Jul 22, 2022 at 1:13 PM David T. Lewis lewis@mail.msen.com wrote:
On Fri, Jul 22, 2022 at 08:06:19AM -0700, Eliot Miranda wrote:
Hi Dave,
On Jul 22, 2022, at 7:53 AM, David T. Lewis lewis@mail.msen.com
wrote:
???On Fri, Jul 22, 2022 at 07:38:07AM -0700, Eliot Miranda wrote:
On Jul 22, 2022, at 3:13 AM, Marcel Taeumel marcel.taeumel@hpi.de
wrote:
??? Hi Eliot --
- the update fails with a merge conflict in the release builder
between: [...]
If you want to prepare a VMMaker Trunk image, you would use a
regular Trunk image, not a release image. I think. So, why aren't you using a recent 6.1alpha image?
-> http://files.squeak.org/6.1alpha/Squeak6.1alpha-22134-64bit/
OK, I???ll try that. Thanx!!
This will probably work with the 6.0 release image:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image
UpdateSqueakTrunkImage.st --doit 'Project current addDeferredUIMessage: [PreferenceWizardMorph allInstances do: [:e | e delete]]'
Or maybe just add "PreferenceWizardMorph allInstances do: [:e | e
delete]." as the first line of the script.
Given that there seems to be a drop event generated somewhere that may
cause the script to be launched again later, is there a way of asking if the script is tuning in the context of DoItFirst? Then the first line would be
self isRunningAsDoItFirst ifTrue: [^self]. ???do stuff second time around when the system is headful???It's best to do only very minimal things in any of the DoItFirst options. These run at the very earliest possible time in the startup list processing, so many things have not yet been initialized at that point. For doing anything non-trivial, you will want to use the normal start up script loader (as you already are doing for the VMMaker scripts).
I'm not trying to use DoItFirst. I'm just trying to load scripts as used to work. Now, once I revert back to the old syntax of vmexe image.image script.st scripts run, but every time a script is run a Note stating Cannot start a second instance of Squeak\with the image "{1}"\because the VM is configured as singleton application.
Why is that happening? It shouldn't, right?
The --doit option (and similar) is just a hook for running a snippet
prior to startup processing, which is helpful if you have a broken image that you need to repair before it goes through the full startup list. Or you can use it to evaluate some expressions prior to running your actual script file.
Dave
We need a page that specifies the startup semantics in the Squeak Help.
_,,,^..^,,,_ best, Eliot
On linux (ARM64 that is in this case) it still works as it has for decades; the after-image-name argument is treated as a URL and gets loaded, with a progress bar showing and I can make it open a Workspace with contents etc. This is how it should be.
I see that the error Eliot gets is in MorphicProject>>#launchSystemFiles:event: which is sent by HandMorph>>#generateDropFilesEvent: which tells us that somebody somewhere is making a drop event on Windows (it is Windows, yes? ) and that might well the the OS trying to be 'helpful'.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Dukedom: aristocratic birth control
Am Sa., 23. Juli 2022 um 19:17 Uhr schrieb tim Rowledge tim@rowledge.org:
[...] somebody somewhere is making a drop event on Windows (it is Windows, yes? ) and that might well the the OS trying to be 'helpful'.
Nope, this is not Windows's doing. It is the VM:
https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/41e16daa6bde22ca494f1... https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/cd1ecfe3ab7cb01e435ef... https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/cd1ecfe3ab7cb01e435ef... https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/d494240736f7c0309e3e8...
But this particular flow seems to require that RunSingleApp=1 be set in the squeak.ini file.
Other maybe related thread: http://lists.squeakfoundation.org/pipermail/squeak-dev/2020-October/thread.h... https://lists.squeakfoundation.org/pipermail/squeak-dev/2020-November/thread...
Hi Marcel,
On Jul 22, 2022, at 3:13 AM, Marcel Taeumel marcel.taeumel@hpi.de wrote:
Hi Eliot --
- the update fails with a merge conflict in the release builder between: [...]
If you want to prepare a VMMaker Trunk image, you would use a regular Trunk image, not a release image. I think. So, why aren't you using a recent 6.1alpha image? -> http://files.squeak.org/6.1alpha/Squeak6.1alpha-22134-64bit/
Thinking about this done more, if used to be that one could start from a 5.3 release image, change the updated url to trunk, abc update to a current trunk. If there was a successor version to the 6.0 release ReleaseBuilder package version in trunk, and perhaps configuration to force if you be loaded, then the conflict could be avoided. One would start from a 6.0 release image, change the update url to trunk, and update. Things would continue to work as before.
Best, Marcel
Am 22.07.2022 05:06:27 schrieb Eliot Miranda eliot.miranda@gmail.com:
Hi All,
ok, this is a bit of a disaster. The invocation is now:Squeak.app/Contents/MacOS/Squeak trunk6-64.image UpdateSqueakTrunkImage.st
Why was it changed?
And the result:
- the update fails with a merge conflict in the release builder between: SystemVersion newVersion: 'Squeak6.0'
and SystemVersion newVersion: 'Squeak6.1alpha'
- a Note that says 'Cannot start a second instance of Squeak
with the image "UpdateSqueakTrunkImage.st" because the VM is configured as singleton application.' becauser somewhere something is generating a DropFileEvent for the UpdateSqueakTrunkImage.st file. The system shouldn't be both executing the script argument and generating a drop file event for it.
The effective result is that I can't automate building a VMMaker image as I was once able to. :-(
On Thu, Jul 21, 2022 at 6:23 PM Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
I'm trying ot update the VMMaker image build scripts. I've got as far as downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!).How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress?
I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st
where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_ best, Eliot
-- _,,,^..^,,,_ best, Eliot
Am I really expected to rewrite all of these, or is the change in semantics actually a bug?
buildsistareader64image.sh:echo $VM trunksista64reader.image -- LoadFFI.st buildsistareader64image.sh:$VM trunksista64reader.image -- LoadFFI.st buildsistareader64image.sh:echo $VM trunksista64reader.image -- LoadReader.st buildsistareader64image.sh:$VM trunksista64reader.image -- LoadReader.st buildsistareader64image.sh:echo $VM trunksista64reader.image -- StartReader.st buildsistareader64image.sh:$VM trunksista64reader.image -- StartReader.st buildsistareaderimage.sh:echo $VM sistareader.image -- LoadSistaSupport.st buildsistareaderimage.sh:$VM sistareader.image -- LoadSistaSupport.st buildsistareaderimage.sh:echo $VM sistareader.image -- LoadReader.st buildsistareaderimage.sh:$VM sistareader.image -- LoadReader.st buildsistareaderimage.sh:echo $VM sistareader.image -- StartReader.st buildsistareaderimage.sh:$VM sistareader.image -- StartReader.st buildspurtrunk64image.sh:echo $VM SpurVMMaker.image -- BuildSpurTrunk64Image.st buildspurtrunk64image.sh:$VM SpurVMMaker.image -- BuildSpurTrunk64Image.st buildspurtrunkreader64image.sh: echo $VM spurreader-64.image -- LoadFFI.st buildspurtrunkreader64image.sh: $VM spurreader-64.image -- LoadFFI.st buildspurtrunkreader64image.sh:echo $VM spurreader-64.image -- LoadReader.st buildspurtrunkreader64image.sh:$VM spurreader-64.image -- LoadReader.st buildspurtrunkreader64image.sh:echo $VM spurreader-64.image -- StartReader.st buildspurtrunkreader64image.sh:$VM spurreader-64.image -- StartReader.st buildspurtrunkreaderimage.sh: echo $VM spurreader.image -- LoadFFI.st buildspurtrunkreaderimage.sh: $VM spurreader.image -- LoadFFI.st buildspurtrunkreaderimage.sh:echo $VM spurreader.image -- LoadReader.st buildspurtrunkreaderimage.sh:$VM spurreader.image -- LoadReader.st buildspurtrunkreaderimage.sh:echo $VM spurreader.image -- StartReader.st buildspurtrunkreaderimage.sh:$VM spurreader.image -- StartReader.st buildspurtrunkvmmaker64image.sh:echo $VM Spur64VMMaker.image -- BuildSqueakSpurTrunkVMMakerImage.st buildspurtrunkvmmaker64image.sh:$VM Spur64VMMaker.image -- BuildSqueakSpurTrunkVMMakerImage.st buildspurtrunkvmmakerimage.sh:echo $VM SpurVMMaker.image -- BuildSqueakSpurTrunkVMMakerImage.st buildspurtrunkvmmakerimage.sh:$VM SpurVMMaker.image -- BuildSqueakSpurTrunkVMMakerImage.st envvars.sh:if unzip --help >/dev/null; then getsqueak50.sh: if unzip --help >/dev/null; then updatespur64SistaV1image.sh: echo $VM $BASESISTA64.image -- NukePreferenceWizardMorph.st updatespur64SistaV1image.sh: $VM $BASESISTA64.image -- NukePreferenceWizardMorph.st updatespur64SistaV1image.sh: echo $VM $BASESISTA64.image -- SaveAsSista.st updatespur64SistaV1image.sh: $VM $BASESISTA64.image -- SaveAsSista.st updatespur64SistaV1image.sh: echo $VM $BASESISTA64.image -- NukePreferenceWizardMorph.st updatespur64SistaV1image.sh: $VM $BASESISTA64.image -- NukePreferenceWizardMorph.st updatespur64SistaV1image.sh:echo $VM $BASESISTA64.image -- UpdateSqueakTrunkImage.st updatespur64SistaV1image.sh:$VM $BASESISTA64.image -- UpdateSqueakTrunkImage.st updatespur64image.sh: echo $VM $BASE64.image -- NukePreferenceWizardMorph.st updatespur64image.sh: $VM $BASE64.image -- NukePreferenceWizardMorph.st updatespur64image.sh:echo $VM $BASE64.image -- UpdateSqueakTrunkImage.st updatespur64image.sh:$VM $BASE64.image -- UpdateSqueakTrunkImage.st updatespurimage.sh: echo $VM $BASE.image -- NukePreferenceWizardMorph.st updatespurimage.sh: $VM $BASE.image -- NukePreferenceWizardMorph.st updatespurimage.sh:echo $VM $BASE.image -- UpdateSqueakTrunkImage.st updatespurimage.sh:$VM $BASE.image -- UpdateSqueakTrunkImage.st updatevmmakerimage.sh:echo $VM SpurVMMaker.image -- UpdateSqueakTrunkImage.st updatevmmakerimage.sh:$VM SpurVMMaker.image -- UpdateSqueakTrunkImage.st
On Thu, Jul 21, 2022 at 6:23 PM Eliot Miranda eliot.miranda@gmail.com wrote:
Hi All,
I'm trying ot update the VMMaker image build scripts. I've got as faras downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!).
How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress?
I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st
where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_ best, Eliot
Hi Eliot --
buildsistareader64image.sh:echo $VM trunksista64reader.image -- LoadFFI.st
So, you are saying that the "--" syntax changed? Hmm... I never used it on Windows.
Actual changes in this area were made end of 2020: http://wiki.squeak.org/squeak/6655
Smalltalk arguments ==> the command line arguments intended for use in the image after all startup processing Smalltalk rawArguments ==> same as above, but also including image name and '‑‑' tokens. Regardless of the various combinations of '‑‑' tokens and Squeak preferences, "Smalltalk arguments" provides of list of arguments intended for use in Squeak after the VM option processing and the startup document processing. This argument list may be used for any purpose at all within the image.
Best, Marcel Am 22.07.2022 05:09:11 schrieb Eliot Miranda eliot.miranda@gmail.com: Am I really expected to rewrite all of these, or is the change in semantics actually a bug?
buildsistareader64image.sh:echo $VM trunksista64reader.image -- LoadFFI.st buildsistareader64image.sh:$VM trunksista64reader.image -- LoadFFI.st buildsistareader64image.sh:echo $VM trunksista64reader.image -- LoadReader.st buildsistareader64image.sh:$VM trunksista64reader.image -- LoadReader.st buildsistareader64image.sh:echo $VM trunksista64reader.image -- StartReader.st buildsistareader64image.sh:$VM trunksista64reader.image -- StartReader.st buildsistareaderimage.sh:echo $VM sistareader.image -- LoadSistaSupport.st buildsistareaderimage.sh:$VM sistareader.image -- LoadSistaSupport.st buildsistareaderimage.sh:echo $VM sistareader.image -- LoadReader.st buildsistareaderimage.sh:$VM sistareader.image -- LoadReader.st buildsistareaderimage.sh:echo $VM sistareader.image -- StartReader.st buildsistareaderimage.sh:$VM sistareader.image -- StartReader.st buildspurtrunk64image.sh:echo $VM SpurVMMaker.image -- BuildSpurTrunk64Image.st buildspurtrunk64image.sh:$VM SpurVMMaker.image -- BuildSpurTrunk64Image.st buildspurtrunkreader64image.sh: echo $VM spurreader-64.image -- LoadFFI.st buildspurtrunkreader64image.sh: $VM spurreader-64.image -- LoadFFI.st buildspurtrunkreader64image.sh:echo $VM spurreader-64.image -- LoadReader.st buildspurtrunkreader64image.sh:$VM spurreader-64.image -- LoadReader.st buildspurtrunkreader64image.sh:echo $VM spurreader-64.image -- StartReader.st buildspurtrunkreader64image.sh:$VM spurreader-64.image -- StartReader.st buildspurtrunkreaderimage.sh: echo $VM spurreader.image -- LoadFFI.st buildspurtrunkreaderimage.sh: $VM spurreader.image -- LoadFFI.st buildspurtrunkreaderimage.sh:echo $VM spurreader.image -- LoadReader.st buildspurtrunkreaderimage.sh:$VM spurreader.image -- LoadReader.st buildspurtrunkreaderimage.sh:echo $VM spurreader.image -- StartReader.st buildspurtrunkreaderimage.sh:$VM spurreader.image -- StartReader.st buildspurtrunkvmmaker64image.sh:echo $VM Spur64VMMaker.image -- BuildSqueakSpurTrunkVMMakerImage.st buildspurtrunkvmmaker64image.sh:$VM Spur64VMMaker.image -- BuildSqueakSpurTrunkVMMakerImage.st buildspurtrunkvmmakerimage.sh:echo $VM SpurVMMaker.image -- BuildSqueakSpurTrunkVMMakerImage.st buildspurtrunkvmmakerimage.sh:$VM SpurVMMaker.image -- BuildSqueakSpurTrunkVMMakerImage.st envvars.sh:if unzip --help >/dev/null; then getsqueak50.sh: if unzip --help >/dev/null; then updatespur64SistaV1image.sh: echo $VM $BASESISTA64.image -- NukePreferenceWizardMorph.st updatespur64SistaV1image.sh: $VM $BASESISTA64.image -- NukePreferenceWizardMorph.st updatespur64SistaV1image.sh: echo $VM $BASESISTA64.image -- SaveAsSista.st updatespur64SistaV1image.sh: $VM $BASESISTA64.image -- SaveAsSista.st updatespur64SistaV1image.sh: echo $VM $BASESISTA64.image -- NukePreferenceWizardMorph.st updatespur64SistaV1image.sh: $VM $BASESISTA64.image -- NukePreferenceWizardMorph.st updatespur64SistaV1image.sh:echo $VM $BASESISTA64.image -- UpdateSqueakTrunkImage.st updatespur64SistaV1image.sh:$VM $BASESISTA64.image -- UpdateSqueakTrunkImage.st updatespur64image.sh: echo $VM $BASE64.image -- NukePreferenceWizardMorph.st updatespur64image.sh: $VM $BASE64.image -- NukePreferenceWizardMorph.st updatespur64image.sh:echo $VM $BASE64.image -- UpdateSqueakTrunkImage.st updatespur64image.sh:$VM $BASE64.image -- UpdateSqueakTrunkImage.st updatespurimage.sh: echo $VM $BASE.image -- NukePreferenceWizardMorph.st updatespurimage.sh: $VM $BASE.image -- NukePreferenceWizardMorph.st updatespurimage.sh:echo $VM $BASE.image -- UpdateSqueakTrunkImage.st updatespurimage.sh:$VM $BASE.image -- UpdateSqueakTrunkImage.st updatevmmakerimage.sh:echo $VM SpurVMMaker.image -- UpdateSqueakTrunkImage.st updatevmmakerimage.sh:$VM SpurVMMaker.image -- UpdateSqueakTrunkImage.st
On Thu, Jul 21, 2022 at 6:23 PM Eliot Miranda <eliot.miranda@gmail.com [mailto:eliot.miranda@gmail.com]> wrote:
Hi All,
I'm trying ot update the VMMaker image build scripts. I've got as far as downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!).
How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress?
I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st
where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_
best, Eliot
--
_,,,^..^,,,_
best, Eliot
Hi Eliot --
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein
Well, that "--filein" is the mechanism of "DoItFirst" and not the good-old start-up *.st script. DoItFirst is triggered way too early for a typical script. Just do it as always then? "./vm my.image startup.st" would be my best guess.
Best, Marcel Am 22.07.2022 03:24:07 schrieb Eliot Miranda eliot.miranda@gmail.com: Hi All,
I'm trying ot update the VMMaker image build scripts. I've got as far as downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!).
How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress?
I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st
where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_
best, Eliot
David, Marcel,
On Jul 22, 2022, at 6:03 AM, Marcel Taeumel marcel.taeumel@hpi.de wrote:
Hi Eliot --
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein
Well, that "--filein" is the mechanism of "DoItFirst" and not the good-old start-up *.st script. DoItFirst is triggered way too early for a typical script. Just do it as always then? "./vm my.image startup.st" would be my best guess.
Does it make sense then to have DoItFirst intercept — as a first argument and arrange that what follows is done later?
What about the drop files event? Perhaps DoItFirst should intercept — and do nothing, leaving if yo whatever generates the drop files event to initiate processing. I will experiment.
Best, Marcel
Am 22.07.2022 03:24:07 schrieb Eliot Miranda eliot.miranda@gmail.com:
Hi All,
I'm trying ot update the VMMaker image build scripts. I've got as far as downloading the latest 6.x image and VM (much easier now; thanks to everyone who has made the github pages easier to navigate!!).How do I launch a trunk6 image with a script so that the system is running headful and one can see it make progress?
I am launching with this on MacOS: and I get a headless blank screen that appears to be 640x480, quite different to the normal startup showing the configuration wizard I get f I launch without the arguments:
./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- UpdateSqueakTrunkImage.st
where trunk6-64.image is a clone of e.g. Squeak6.0-22104-64bit.image
I've tried ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image -- --filein UpdateSqueakTrunkImage.st ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image --filein UpdateSqueakTrunkImage.st etc, but get the 640x480 grey screen image. _,,,^..^,,,_ best, Eliot
squeak-dev@lists.squeakfoundation.org
-
David T. Lewis -
Eliot Miranda -
Jakob Reschke -
Marcel Taeumel -
tim Rowledge