[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-windows
Subject:    Re: Basic craft Mac questions
From:       Thomas Friedrichsmeier <thomas.friedrichsmeier () ruhr-uni-bochum ! de>
Date:       2020-01-04 9:46:55
Message-ID: 20200104104655.7e24e15d () edge
[Download RAW message or body]


On Sat, 4 Jan 2020 22:00:43 +1300
Ben Cooksley <bcooksley@kde.org> wrote:

[...]

> Given the issues people have had with the latest version of MacOS
> (Catalina) I don't intend on updating it anytime soon.
> We were forced to upgrade if memory serves by requirements in Qt
> itself, so that is a limiting factor to a certain extent.
> 
> I'm a bit surprised that we're not able to target older versions of
> MacOS though even though we're running on a newer version ourselves
> (all our Windows builds are done on Win 10 machines, yet the final
> product can be run fine on Windows 7)

From the little that I have gathered, you need to (download and)
instruct XCode to use an older (supported) SDK, explicitly.

For what it's worth, for showing the minimum required version of a
binary:

otool -l /path/to/binary | grep --after-context=4 "LC_BUILD_VERSION"

> > > 2) Is there any chance of getting signed installers on Mac? That
> > > seems to be the only thing missing from a really smooth
> > > installation experience.  
> >
> > I see that craft already has code for signing, but apparently it is
> > not (currently) used on the binary-factory. Could that be changed?  
> 
> Doesn't this require an Apple Developer ID?

I suppose so. I thought we might have one for this purpose.
 
> Note that even signing doesn't help on Catalina, as I believe that
> started requiring all applications to be notarised by Apple.

Ouch, if that is so.

Regards
Thomas

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]