An unofficial repository of libQt5Pas libraries to help fill in until the distros catch up.

Whats here
So far, x86_64, i686 (ie 32bit) armhf and arm64 (ie aarch64) versions available, debs, rpm and tgz

Note : If you are using a current Arch Linux, Debian Trixie (13) or Ubuntu 24.04/24.10 or Fedora 41 you don't need the Qt5 libraries, the ones in your distro repo will be fine. Probably (1.2.16 is slightly newer that the ones in the distros mentioned above so, its just possible you may need that recent update.

Note : some RPM users, particularly OpenSUSE will need to register the key file that the RPM packages were signed with. I use the same keyfile as my tomboy-ng project, details here - https://github.com/tomboy-notes/tomboy-ng/wiki/Download_Release#opensuse

Please advise if they do not appear to install or work as expected.

Care is needed in selecting the right package or packages. Some help

• Packages with -devel or -dev in their names are development packages, only needed if you are compiling (using Lazarus and FPC) apps. If you are just using an app built elsewhere, you don't need a development package.
• The packages with x86_64 or amd64 in their names are for Intel/AMD 64 bit systems.
• The packages with i386 (debs) or i686 (RPMs) and for Intel 32bit systems.
• The packages with armv7l in their names are for 32bit arm chips such as (early) Raspberry Pi.
• The packages ending in .rpm are for Fedora and other rpm dependent systems.
• The packages ending in .deb are for Debian, Ubuntu, Mint and other deb based systems.
• The packages ending in tar.gz are contain just a binary library, they are for experienced Linux users who will untar the file and manually put the library in the right place. See the targz.readme.

Github like to hide the files offered here (no, I don't know why), so if you don't see what you need, click the small black triangle.

Davo

Whats new
Zeljan says "removed QTimer_singleShot4() overload because it cannot be used with Qt5 < 5.10"

Whats here

• x86_64, i386 (ie Intel 32bit), amd64, armhf (eg RaspberryPi 32bit) and aarch64 (eg RaspberryPi 64bit, NOT Mac) - deb, rpm and tarball,

Note : If you are using Debian Trixie (13) or Ubuntu 24.04 then you do NOT need the Qt5 version here, your repo version will be fine. As far as I know, sadely no distro currently has a usable libQt6Pas yet.

Note : some RPM users, particularly OpenSUSE will need to register the key file that the RPM packages were signed with. I use the same keyfile as my tomboy-ng project, details here - https://github.com/tomboy-notes/tomboy-ng/wiki/Download_Release#opensuse

Prior to December 2023, some RPM packages here were unsigned, my apologies !

Please advise if they do not appear to install or work as expected.

Care is needed in selecting the right package or packages. Some help

• Packages with -devel or -dev in their names are development packages, only needed if you are compiling (using Lazarus and FPC) apps. If you are just using an app built eleswhere, you don't need a development package.
• The packages with x86_64 or amd64 in their names are for Intel/AMD 64 bit systems.
• The packages with i386 (debs) or i686 (RPMs) and for Intel 32bit systems.
• The packages with armv7l in their names are for 32bit arm chips such as (early) Raspberry Pi.
• The packages ending in .rpm are for Fedora and other rpm dependent systems.
• The packages ending in .deb are for Debian, Ubuntu, Mint and other deb based systems.
• The packages ending in tar.gz are contain just a binary library, they are for experienced Linux users who will untar the file and manually put the library in the right place. See the targz.readme.

Repackaging of RPM packages
Has become necessary to ensure that the packages will overwrite older packages from your distro repo. Seems that every distro likes to name its packages differently. Further, to strive for some consistency, I have dropped the left most "1." from the version numbers (so, what is really 1.2.15 is now presented here as 2.15). Some distros kept that "1." as part of the package name (Mageia etc, some did not, eg Fedora, we don't anymore). There is no functional differences in the libraries them selves, its just packaging and rules associated with installing.

The packages with a "-3" after the main version number are the updated ones. I will do all of them over the next few days.

Whats new
Zeljan says "Qt5: use QTimer::singleShot() with QObject context from Qt 5.9.0"

Whats here

• x86_64, amd64 - deb, rpm and tarball,

• armhf, armv7l - 32bit OS for Raspberry Pi will follow when i return home from current travels.

If time permits, I might also do the following if it seems someone needs them -

• aarch64, arm64 - 64bit arm, newer OS for Raspberry Pi and others.

I am afraid no testing has been done, I am away from home at present, please let me know if you see anything unexpected.

Care is needed in selecting the right package or packages. Some help

• Packages with -devel or -dev in their names are development packages, only needed if you are compiling (using Lazarus and FPC) apps. If you are just using an app built eleswhere, you don't need a development package.
• The packages with x86_64 or amd64 in their names are for Intel/AMD 64 bit systems.
• The packages with armv7l in their names are for 32bit arm chips such as (early) Raspberry Pi.
• The packages ending in .rpm are for Fedora and other rpm dependent systems.
• The packages ending in .deb are for Debian, Ubuntu, Mint and other deb based systems.
• The packages ending in tar.gz are contain just a binary library, they are for experienced Linux users who will untar the file and manually put the library in the right place. See the targz.readme.

So far we have -

• x86_64, amd64 - deb, rpm and tarball, armhf, armv7l - 32bit OS for Raspberry Pi

If time permits, I might also do the following if it seems someone needs them -

• aarch64, arm64 - 64bit arm, newer OS for Raspberry Pi and others.

I am afraid not a lot of testing has been done, please let me know if you see anything unexpected.

Care is needed in selecting the right package or packages. Some help

• Packages with -devel or -dev in their names are development packages, only needed if you are compiling (using Lazarus and FPC) apps. If you are just using an app built eleswhere, you don't need a development package.
• The packages with x86_64 or amd64 in their names are for Intel/AMD 64 bit systems.
• The packages with armv7l in their names are for 32bit arm chips such as (early) Paspberry Pi.
• The packages ending in .rpm are for Fedora and other rpm dependent systems.
• The packages ending in .deb are for Debian, Ubuntu, Mint and other deb based systems.
• The packages ending in tar.gz are contain just a binary library, they are for experienced Linux users who will untar the file and manually put the library in the right place. See the targz.readme.

WARNING - there was a mistake in the x86_64 RPM devel packaging, I have been unable to replicate the process that made a bad package, its now replaced with a good one but if you see something strange building Qt5 apps on an RPM machine, please let me know.

So far we have -

• x86_64, amd64 - deb, rpm and tarball.

To follow as time permits (sorry, consider using the 1.2.11 ones of it works for you) -

• aarch64, arm64 - 64bit arm, newer OS for Raspberry Pi and others.
• armhf, armv7l - 32bit OS for Raspberry Pi

I am afraid not a lot of testing has been done, please let me know if you see anything unexpected.

History
-1 Initial release
-2 Fixes to dev package dependencies.
-3 Fix a naming problem, '1'

Code changes reflecting some small changes to the cbindings inc -

• added QCompleter class to C bindings
• Changed handles types to qintptr (PTRINT) and quintptr (PTRUINT), added QCompleter class

Packaging has changed the way the RPMs are built, no Alien involved, cleaner and correct destination directories.

So far we have -

• x86_64, amd64 - deb, rpm and tarball.
• aarch64, arm64 - 64bit arm, newer OS for Raspberry Pi and others.
• armhf, armv7l - 32bit OS for Raspberry Pi

I am afraid absolutely minimal testing has been done on the arm packages, please let me know if you see anything unexpected.

This release includes some new identifiers that are only required if you are using Lazarus Trunk or Main. Versions 2.2.4 and earlier of Lazarus do not require these new libraries. Please also remember, they will not help you with old distributions using early versions of QT5.

And, of course, they are only required until your distribution catches up to the official releases. Sadly, thats not always as quick as we would like.

Available here are libraries to suit amd64 (and of course intel 64bit) processors as used on almost all desk and laptop machines, arm64 (ie aarch64) and armhf (32bit OS on either 32 or 64bit hardware), used, for example on the Raspberry Pi.

As is generally the case in open source, no absolute guarantee of usefulness or even safety in your use case can be offered. But if you do have a problem, please let me know. Note the arm rpms have no been tested, I don't have any rpm OS running on Raspberry Pi to test on. But I'm reasonably confident they will be fine. If your experience is otherwise, please let me know. Further, the arm rpms have not been signed, as that only a SUSE thing, I have not bothered. If you are using OpenSUSE on a Raspberry Pi, sorry, give me a yell and I will sign them using the same key as I use for tomboy_ng.

Also provided, for the experienced user are gzipped tarballs of just a appropriate library and a short readme that can be manually installed. Please choose carefully.

Most people will want the ones that have "x86_64" in the file name.

Note: The Qt6 libraries now live in https://github.com/davidbannon/libqt6pas

libqt5pas now supports some accessibility features that have been added to the Lazarus Widget Set. These changes were made in April 2021 to Lazarus trunk, its possible that they will not appear in the standard distro repos for some time. Until then, hopefully the packages here will be of some assistance.

Note that I have not personally tested the new features, your feed back is needed !

These packages may be useful. If you use Ubuntu 18.04 or Mageia 7.1 and need to use Lazarus Qt5 apps, almost certainly. If you use newer Linux distro and a Lazarus Qt5 app that depends on newer features or bug fixes, maybe.

Only developers need to use the dev packages.

This is the first release under this model and must have further testing before trust ! Please report your experiences.

Note : Its suggested that the next 'release' be called 1.3.206, reflecting its relationship with Lazarus 2.0.6. That will achieve our aim of having a version number greater than all the various existing releases based on old code. Please consider commenting on this either via an 'issue' here or posting to https://forum.lazarus.freepascal.org/index.php/topic,48889.msg353900.html. If I get some indication that others think this is a good approach, I'll contact the various Linux distributions.