You must use libQt5Pas from lazarus trunk - in other words you must rebuild libQt5Pas on your own since I've added QAccessibility* in trunk.
If you don't want to build libQt5Pas then use stable Lazarus release.
cd lcl/interfaces/qt5/cbindings
qmake -query && qmake && make
You must install qt5 dev packages (don't know exact names)
I've copied libQt5Pas.so.1.2.9 manually after compilation.
cd lcl/interfaces/qt5/cbindings
qmake -query && qmake && make
Users need to reinstall libqt5Pas. If they use app from Lazarus trunk.
From 'releases' from here
https://github.com/davidbannon/libqt5pas/
"Replace" would be more appropriate, ...
..... with the numbering rationale being in https://github.com/davidbannon/libqt5pas/blob/master/README.md
If my understanding is correct Debian's 2.6 corresponds to his 1.2.6 etc.
Building from lazarus/trunk sources looks like a problem on a comparatively clean system,
I'm watching with interest. In the interim do you have any suggestion what packages are the minimum required for building? I think that would be of interest to anybody who occasionally rebuilds lazarus-trunk since by and large we'd expect to have the development tools and libraries applicable to our OS etc. available as a prerequisite.
MarkMLl
As I mentioned above, qmake and libqt5x11extras-dev. Probably will have everything else.
Debian Testing is in a feature freeze mode now, wonder if we should be pushing to get this "new and improved" lib into it ? Will have to test to see it does not break Lazarus 2.0.12 for example. Sigh ...
If anybody does fix this (or becomes aware of its having been fixed) in a way that doesn't need a locally-generated binding library please could they append something to this thread so that we all know.
Personally, I think the accessibility changes made to Lazarus's Qt5 might be better done with an opt in #DEFINE approach.
I've not got the relevant code in front of me at the moment, but is it safe to conclude that a substantial number of those changes are declarative so don't depend on the binary (shared object) of the updated binding?You mean as long as they are not called, it does not matter that they point nowhere ? A good number but not more that 20% as a guess.
Could the changes be reduced to a small number of function calls which could be handled using run-time dynamic linkage?No, not without restructuring Z's code, not something I am not willing to risk !
But the real question is, are the Powers that Be willing to accept such an ugly hack ? It would probably have to be in there for at least two to three years ?
May I suggest that we finally move libqt5pas into the Lazarus source tree (where the other qt5 widgetset code is living), maintain it ourselves and build it along with Lazarus?
also Ubuntu LTS