Please help testing upcoming openMSX release!

Page 48/61
41 | 42 | 43 | 44 | 45 | 46 | 47 | | 49 | 50 | 51 | 52 | 53

By Grauw

Ascended (10063)

Grauw's picture

09-12-2020, 21:35

sdsnatcher73 wrote:

I wondered before why openMSX for macOS targets 10.7 that seems such an ancient OS. I think if you change the target to 10.13 (even for your private build) it will probably work fine again. Another option may be that Qt5 is handled as a 3rd party external during the build (and as such also build with 10.7 as target).

Ah, if the target version is increased, I kindly request at least 10.12, since when I was looking into Metal and touch bar support last year, I wanted to use some APIs from that version.

macOS 10.12 and 10.13 min spec is Macs from 2009/2010. macOS 10.14 and 10.15 min spec is systems from around 2012. macOS 11.0 min spec is 2013/2014.

I think 10.13 (High Sierra) seems a fine choice, relatively modern while still supporting older systems.

By Manuel

Ascended (18148)

Manuel's picture

10-12-2020, 00:27

As no main dev has a Mac, I'm hoping you guys will help us to provide patches and test them on your Macs.

By sdsnatcher73

Prophet (2234)

sdsnatcher73's picture

10-12-2020, 08:43

Grauw][quote=sdsnatcher73 wrote:

I think 10.13 (High Sierra) seems a fine choice, relatively modern while still supporting older systems.

I agree, this would include basically the last 4 major releases. I will give it a shot later today..

By ericb59

Paragon (1046)

ericb59's picture

10-12-2020, 15:17

perhaps a problem with QT ?
https://bugreports.qt.io/browse/QTBUG-85546

By sdsnatcher73

Prophet (2234)

sdsnatcher73's picture

10-12-2020, 17:47

After changing minimal OS version to 10.13 the debugger works fine on my machine (2020 MacBook Air running macOS 11.0.1). Well the debugger starts and is able to connect, I am not familiar in it's usage Wink

If you guys want to try it out please download openMSX.app.zip and openMSX-debugger.app.zip and let me know how it goes on your machines. If it is working fine than I will create pull requests to the official repos.

By Sylvester

Hero (536)

Sylvester's picture

10-12-2020, 19:13

Just tested it, the debugger starts, but it has the same problems as the screenshot I posted before. The code View is missing some text (i guess it's white on white) and the Main Memory table is messed up.

By sdsnatcher73

Prophet (2234)

sdsnatcher73's picture

10-12-2020, 20:41

Hmm, guess there are 2 issues then.
1. Linking warnings which disappear when the target is changed to 10.13
2. Qt issues rendering the app on macOS 11.0 (which are most likely related to the issue ericb59 referred to).

By Grauw

Ascended (10063)

Grauw's picture

10-12-2020, 21:20

I built openMSX 75c0860 from source, and encountered no issues.

Also with OSX_VER:=10.13 it works fine, although there are some deprecation warnings:

src/file/FileOperations.cc:87:6: warning: 'GetCurrentProcess' is deprecated: first deprecated in macOS 10.9
src/file/FileOperations.cc:91:6: warning: 'GetProcessBundleLocation' is deprecated: first deprecated in macOS 10.9
src/file/FileOperations.cc:97:6: warning: 'FSGetCatalogInfo' is deprecated: first deprecated in macOS 10.8
src/file/FileOperations.cc:106:6: warning: 'FSGetVolumeInfo' is deprecated: first deprecated in macOS 10.8
src/file/FileOperations.cc:119:7: warning: 'FSOpenIterator' is deprecated: first deprecated in macOS 10.8
src/file/FileOperations.cc:130:16: warning: 'FSGetCatalogInfoBulk' is deprecated: first deprecated in macOS 10.8
src/file/FileOperations.cc:162:24: warning: 'FSCloseIterator' is deprecated: first deprecated in macOS 10.8
src/file/FileOperations.cc:166:11: warning: 'FSRefMakePath' is deprecated: first deprecated in macOS 10.8
src/file/FileOperations.cc:176:20: warning: 'FSCloseIterator' is deprecated: first deprecated in macOS 10.8
src/file/FileOperations.cc:179:7: warning: 'FSCompareFSRefs' is deprecated: first deprecated in macOS 10.8
src/file/FileOperations.cc:183:7: warning: 'FSGetCatalogInfo' is deprecated: first deprecated in macOS 10.8

I built openMSX Debugger 77b1f1e from source, and encountered the warnings mentioned by sdsnatcher73 about the target version being 10.7 rather than 10.13, but otherwise no issues.

ld: warning: dylib (/usr/local/Cellar/qt/5.15.2/lib/QtNetwork.framework/QtNetwork) was built for newer macOS version (10.13) than being linked (10.7)
ld: warning: dylib (/usr/local/Cellar/qt/5.15.2/lib/QtCore.framework/QtCore) was built for newer macOS version (10.13) than being linked (10.7)
ld: warning: dylib (/usr/local/Cellar/qt/5.15.2/lib/QtWidgets.framework/QtWidgets) was built for newer macOS version (10.13) than being linked (10.7)
ld: warning: dylib (/usr/local/Cellar/qt/5.15.2/lib/QtGui.framework/QtGui) was built for newer macOS version (10.13) than being linked (10.7)
ld: warning: dylib (/usr/local/Cellar/qt/5.15.2/lib/QtXml.framework/QtXml) was built for newer macOS version (10.13) than being linked (10.7)

With OSX_VER:=10.13 the linker warnings disappear. A bunch of Qt deprecation warnings remain.

Using macOS Catalina 10.15.7 with XCode 12.2 and Qt 5.15.2.

By Grauw

Ascended (10063)

Grauw's picture

11-12-2020, 18:15

I increased the openMSX target macOS version to 10.13 High Sierra and replaced the deprecated code that was causing the warnings mentioned above. As an intended side-effect, the build now also supports Objective-C to interface with macOS APIs.

(I didn’t touch the debugger.)

By sdsnatcher73

Prophet (2234)

sdsnatcher73's picture

11-12-2020, 20:29

Cool! Great work Grauw.

Page 48/61
41 | 42 | 43 | 44 | 45 | 46 | 47 | | 49 | 50 | 51 | 52 | 53