You don't recompile qt5.pas but Qt5Pas C bindings.
OK, makes sense. And worked fine. Thanks zeliko !
I prefer when it's builded by distro and can be installed via package manager,
Yes, agree 100% but the touble is that there are too many combinations for that to work (?). As I understand it, libQt5Pas needs to match the compiler the app was built from, not the distro itself ? So, if someone has, lets say, a QT5 app built using Lazarus 1.6 it might need a different library than a second app built using Lazarus 2.0.0 ? So, if they update their library, the older app may stop working ?
but sure, you can build it on your own and deploy with your app.
hmm, maybe not ? I'd need to build them a library to match the combination of their version of QT and my version of Lazarus, a mistake might mess up their system perhaps ?
Interesting ......
In case someone else wanders across this thread, to build that libQt5Pas library, I did -
- cd to your current Lazarus install and down to lcl/interfaces/qt5/cbindings/ Read the README, its useful.
- I found I had a non functioning qmake, wanted to use no existing qt4 tools. Install (from package manager) qt5-qmake. And then when using it, give its full pathname.
- I had to install (via package manager again) libqt5x11extras5-dev before a successful run of /usr/lib/qt5/bin/qmake
- make <enter> (had an awful lot of work to do, maybe I have got too used to fpc fast compiling !)
- eventually that generated libQt5Pas.so.1.2.6, same name as the one offered in package manager but 40 times the size (degugging stuff still in there ??). I manually copied that to /usr/lib/x86_64-linux-gnu/ (in my case overwriting the repo supplied one). Note needs symlinks to libQt5Pas.so, libQt5Pas.so.1 and libQt5Pas.so.1.2
After that, Lazarus could build my app with Qt5 no probs.
Now to determine if it will run on other machines as easily ....
(Thanks zeljko, would never got this far without your help.)
Davo