Can I build Calibre 4.0 on a native macOS machine running OS X El Capitan 10.11.6? - Page 2

vaboro · 10-09-2019, 07:38 PM

I guess I need to test it on a VM then.

vaboro · 10-11-2019, 06:18 PM

Upgrading from 10.11 to 10.12 breaks Mail.app bundle that is crucial to another client-server application and I cant figure out how to fix that.

KevinH · 10-12-2019, 05:47 PM

I am not seeing this. Mail.app worked just fine on 10.11, 10.12 and still does on 10.13 and there are updates for Mail.app as well.

vaboro · 10-12-2019, 08:49 PM

The Mail.app itself works fine. The software I have on 10.11 has a server part, a client part and also installs a bundle for Mail.app. I tested the server and the client on 10.12 VM. Both worked. But the Mail.app stopped loading the bundle.

KevinH · 10-12-2019, 11:24 PM

I am still not sure exactly what "bundle" you are talking about. Is this custom software you created?

vaboro · 10-13-2019, 12:34 AM

I mean Mail.app extension that is put into /Library/Mail/Bundles folder.
Unfortunately, it's a purchased proprietary software. No access to source code.

I am seeing two options now:

1) build calibre 4 on 10.11 after building all dependencies. At the moment I'm seeing this error https://bugs.launchpad.net/calibre/+bug/1807369 and I guess I have to make sure sip and PyQt5 are compatible.

2) build calibre 4 on 10.12 VM following your instructions and after that try to use it on 10.11

Do you think calibre 4 built on 10.12 runs on 10.11?

KevinH · 10-13-2019, 09:20 AM

Very probably not. The reason is that Apple introduced a few new kernel system calls in 10.12 that simply do not exist in 10.11. Then Qt 5.11.x which ran on 10.11, decided to drop support for macOS 10.11 when they transitioned to Qt 5.12.x and later. In that move all of the ifdefs that were used to support 10.11 were removed and many of the new kernel sys calls only available in 10.12 were used.

So you either must try with Qt5.11.x which was pretty broken on macOS or upgrade to 10.12 and then Qt 5.12.x will build out of the box.

Please note, most standard opensource configure scripts used for most linux platforms are broken on macOS in that they only look at the current headers and ignore the MACOS_DEPLOYMENT_TARGET setting. So they will detect the new kernel calls in 10.12 even if you specify 10.11 as the deployment target. I literally have to patch most configure scripts to build for 10.11 or 10.12 when I use 10.13 or later sdk to prevent the new kernel calls from being detected and used by configure.

This happens in libpng, libjpegturbo, python 3.x, etc.

Unless you are aware of this, it is just easier to build on the version of macOS that you want to deploy for. That is why I am keeping my own dev machines running 10.12 or 10.13 and have not or will not move to 10.14 or later until forced by Qt or other required package.

vaboro · 10-13-2019, 10:33 AM

Thank you! Appreciate your reply very much!

Acanthus · 10-16-2019, 04:37 PM

I'm another user stuck with 10.11.6 and if anyone would succeed in building 4.x on that platform and make the result of their efforts available, they'd make me happy again

.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre 3.41.3 for macOS 10.14.4	adrianf	Library Management	2	04-23-2019 05:15 AM
How to get Calibre 3 running on Raspberry Pi 3 running Raspbian Jessie?	fivestones	Calibre	6	01-25-2018 09:41 PM
Calibre Content Server in El Capitan not starting OK	perezbalen	Devices	2	07-18-2016 02:16 PM
Calibre 2.58 hanging with El Capitan	ursog	Calibre	3	06-12-2016 10:18 AM
What different between HTML5 APP(build by phonegap) & Native APP	sevenxtars	Android Developer's Corner	1	06-29-2012 02:03 AM

10-09-2019, 07:38 PM	#16
vaboro Member Posts: 12 Karma: 10 Join Date: Oct 2019 Device: Kindle DX	I guess I need to test it on a VM then.

10-11-2019, 06:18 PM	#17
vaboro Member Posts: 12 Karma: 10 Join Date: Oct 2019 Device: Kindle DX	Upgrading from 10.11 to 10.12 breaks Mail.app bundle that is crucial to another client-server application and I cant figure out how to fix that.

10-12-2019, 05:47 PM	#18
KevinH Sigil Developer Posts: 8,763 Karma: 5706256 Join Date: Nov 2009 Device: many	I am not seeing this. Mail.app worked just fine on 10.11, 10.12 and still does on 10.13 and there are updates for Mail.app as well.

10-12-2019, 08:49 PM	#19
vaboro Member Posts: 12 Karma: 10 Join Date: Oct 2019 Device: Kindle DX	The Mail.app itself works fine. The software I have on 10.11 has a server part, a client part and also installs a bundle for Mail.app. I tested the server and the client on 10.12 VM. Both worked. But the Mail.app stopped loading the bundle.

10-12-2019, 11:24 PM	#20
KevinH Sigil Developer Posts: 8,763 Karma: 5706256 Join Date: Nov 2009 Device: many	I am still not sure exactly what "bundle" you are talking about. Is this custom software you created?

10-13-2019, 12:34 AM	#21
vaboro Member Posts: 12 Karma: 10 Join Date: Oct 2019 Device: Kindle DX	I mean Mail.app extension that is put into /Library/Mail/Bundles folder. Unfortunately, it's a purchased proprietary software. No access to source code. I am seeing two options now: 1) build calibre 4 on 10.11 after building all dependencies. At the moment I'm seeing this error https://bugs.launchpad.net/calibre/+bug/1807369 and I guess I have to make sure sip and PyQt5 are compatible. 2) build calibre 4 on 10.12 VM following your instructions and after that try to use it on 10.11 Do you think calibre 4 built on 10.12 runs on 10.11?

10-13-2019, 09:20 AM	#22
KevinH Sigil Developer Posts: 8,763 Karma: 5706256 Join Date: Nov 2009 Device: many	Very probably not. The reason is that Apple introduced a few new kernel system calls in 10.12 that simply do not exist in 10.11. Then Qt 5.11.x which ran on 10.11, decided to drop support for macOS 10.11 when they transitioned to Qt 5.12.x and later. In that move all of the ifdefs that were used to support 10.11 were removed and many of the new kernel sys calls only available in 10.12 were used. So you either must try with Qt5.11.x which was pretty broken on macOS or upgrade to 10.12 and then Qt 5.12.x will build out of the box. Please note, most standard opensource configure scripts used for most linux platforms are broken on macOS in that they only look at the current headers and ignore the MACOS_DEPLOYMENT_TARGET setting. So they will detect the new kernel calls in 10.12 even if you specify 10.11 as the deployment target. I literally have to patch most configure scripts to build for 10.11 or 10.12 when I use 10.13 or later sdk to prevent the new kernel calls from being detected and used by configure. This happens in libpng, libjpegturbo, python 3.x, etc. Unless you are aware of this, it is just easier to build on the version of macOS that you want to deploy for. That is why I am keeping my own dev machines running 10.12 or 10.13 and have not or will not move to 10.14 or later until forced by Qt or other required package.

10-13-2019, 10:33 AM	#23
vaboro Member Posts: 12 Karma: 10 Join Date: Oct 2019 Device: Kindle DX	Thank you! Appreciate your reply very much!

10-16-2019, 04:37 PM	#24
Acanthus Junior Member Posts: 2 Karma: 10 Join Date: Jul 2016 Device: Generic	I'm another user stuck with 10.11.6 and if anyone would succeed in building 4.x on that platform and make the result of their efforts available, they'd make me happy again .

Advert

Advert