[KDE/Mac] first krita 3.0 pre-alpha app bundle

[René J.V. Bertin]

On Saturday January 16 2016 09:32:04 Boudewijn Rempt wrote:

>Double-clicking, even from the opened dmg worked for me... But if you can find something that will fix running Krita by simply editing the Info.plist, I would be so happy! Since, evidently,the executable itself works fine, so I wouldn't have to figure out how to build Qt on El Capitan for an older SDK.

What is your Mavericks (10.9) set-up, do you have Xcode installed with the 10.11 SDK? Marko does, and even though it seems unlikely it wouldn't take me by complete surprise if that changes behaviour somehow, explaining the error he sees.

In general it's a safer approach to use the oldest system you want to support for building, either to provide (at least 2) separate packages or by using the SDK for the latest version.
Either way, there is the MACOSX_DEPLOYMENT_TARGET env. variable which allows to control what your build targets, as well as the -mmacosx-version-min=version compiler option.

> What model of Mac do you have, and what GPU?

No AVX, looks like he's running on an i5 though I seem to recall he also has access to an older Core2Duo.
That might in fact also explain the error he's seeing: if 10.11 doesn't run on that model it may be that the system simply makes the shortcut assumption that any application built for 10.11 also won't run there.

> That's normal: it's what I tried to explain earlier. We use QPainter to draw
> on a QOpenGLWidget, and on OSX that works only if your application limits
> itself to OpenGL 2 or 2 ES. We need some features from 3, so have to
> disable the Compatibility Profile and enable the Core Profile, which breaks
> QPainter.

I would say it's "to be expected", not exactly normal ;)
Those features requiring OpenGL 3, how "core" are they? It seems you have a compromise to make between central functionality (like a visible mouse pointer), and feature-set.  Possibly through a setting or toggle somewhere, because I presume that the profiles can be dis- and enabled at runtime?
BTW, does this dilemma exist on all current OS X versions, even the one(s) that don't have the Metal API/SDK/whatever?

NB: toggle to switch off features requiring OpenGL 3 might be useful anyway, to support older hardware. We have an older laptop here with a discrete Radeon adapter that's still perfectly adequate for everything 2D we're likely to throw at it, but it doesn't do OpenGL 3 from what I can see. But maybe that's handled "graciously" on Linux in that OpenGL 3 calls will simply fail without causing the application to abort?

Cheers,
René