[Vm-dev] No more support for running 64-bit VM on macOS < 10.13?
eliot.miranda at gmail.com
Fri Mar 22 00:43:47 UTC 2019
> On Mar 21, 2019, at 3:11 PM, Ronie Salgado <roniesalg at gmail.com> wrote:
> Give me until sunday for refactoring this and supporting the Metal backend, and the old OpenGL backend. I think that it should be possible to select the actual kind of view based on what is available(MTLDevice can be null if not supported), or by providing a command line option in the worst case.
Thanks Ronie! Take the time you need; don’t wreck your weekend. I for one am really thankful for this great work. LMK if I can help test. I have a 10.13 and IIRC a 10.12 system I can test with.
> Best regards,
>> El jue., 21 mar. 2019 a las 16:48, Eliot Miranda (<eliot.miranda at gmail.com>) escribió:
>> Hi Tim,
>>> On Thu, Mar 21, 2019 at 11:18 AM Tim Johnson <digit at sonic.net> wrote:
>>> Is running the 64-bit VM now unsupported on anything less than macOS
>>> (nee OS X) 10.13 or 10.14? Perhaps because of the Metal changes and
>>> OpenGL deprecation...?
>>> I just compiled the 64-bit VM fresh and tried running it on my
>>> 10.12.6 system. I got a Squeak window with no graphics inside (just
>>> blackness) and a message on my terminal console:
>>> 2019-03-21 10:58:55.324 Squeak[70669:4778174] Pipeline state creation
>>> error: Function screenQuadFragmentShader is using language version 2.1
>>> which is incompatible with this OS.
>> My understanding is that this is a temporary situation, the result of Ronie having made an initial Metal implementation which needs to be revised to account for earlier versions. The tip no longer runs on 10.13. i hope that Ronie can solve this, or that I (we?) can work with Ronie to address this serious p[roblem quickly.
>>> If so, I may need to make a choice between:
>>> - upgrading my operating system,
>>> - using the 32-bit VM (though my image is 64-bit),
>>> - staying on an older VM version (though I leave it running for many
>>> days and its memory usage balloons from ~313 megabytes to multiple
>>> gigabytes, perhaps due to the event handling memory leak bug, which I
>>> was hoping to leave behind).
>>> I wonder if it would be worth the effort to handle this situation
>>> gracefully rather than bringing up a non-functioning environment which
>>> requires a force-quit. Perhaps this could be easily accomplished by
>>> including the proper minimum OS version in the Info.plist of the 64-bit
>>> app bundle and letting macOS do the work of disallowing a launch on
>>> older OS versions.
>>> Tim J
>>>  build.macos64x64/squeak.cog.spur
>> best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev