BatchDrake
Build from source - QT6 lrelease not found
I've previously been able to successfully perform a local build of Sigdigger on my computer. I've now downloaded the code again but can not build it any more...
During build from source on Ubuntu 22.04 the system has now started looking for /usr/lib/qt6/bin/lrelease which has never been present on my computer... This might have been started after installing Qt6 packages?
How do I fix this? Something more I need to install, create a symlink, or force SigDigger to use Qt5 istead? I believe lrelease is related to Qt Linguist, which I do have installed (both Qt5 and Qt6 versions).
(Note: I need UHD/USRP support, so I can not use the precompiled SigDigger appimage.)
That's odd, I build SigDigger with Qt6 regularly. Perhaps there are some packages missing? How did you install Qt6?
El sáb., 23 nov. 2024 8:05, Peter Nyman @.***> escribió:
During build from source on Ubuntu 22.04 the system has now started looking for /usr/lib/qt6/bin/lrelease which has never been present on my computer... This might have been started after installing Qt6 packages?
How do I fix this? Something more I need to install, create a symlink, or force SigDigger to use Qt5 istead? I believe lrelease is related to Qt Linguist, which I do have installed (both Qt5 and Qt6 versions).
— Reply to this email directly, view it on GitHub https://github.com/BatchDrake/SigDigger/issues/262, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEVETYLLT2TP3DPJHWLDLT2CASK5AVCNFSM6AAAAABSKYVZAWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY4DKNJUHEZTGNI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Thanks for fast reply! :-)
At first my computer had a some Qt6 packages installed and the old Qt creator provided by Ubuntu, but after I realized this didn't compile, I first installed even more Qt6 packages using apt-get and later installed the latest Qt creator using their online install. Cleared the Sigdigger folders, redownloaded the Sigdigger source code from github once more, and still can not successfully build due to lrelease missing....
(I, (at least try to...), use the "develop" tag of SigDigger and the other components).
Do you know if the /usr/lib/qt6/bin/lrelease file is needed and I need to fix my Qt6 install, or is Qt6 looking for lrelease at the wrong path?
lrelease is a Qt Linguist tool needed for internationalization, perhaps that's the package you need. Truth is, I usually install Qt6 from the official Qt installer, and I am not sure how Ubuntu splits Qt into several packages.
PS have in mind I merged all projects (sigutils, suscan, suwidgets and SigDigger) to master not too long ago, and that's now the current development branch. Make sure you have all the latest changes before building the software.
El sáb., 23 nov. 2024 8:23, Peter Nyman @.***> escribió:
Thanks for fast reply! :-)
At first my computer had a some Qt6 packages installed and the old Qt creator provided by Ubuntu, but after I realized this didn't compile, I first installed even more Qt6 packages using apt-get and later installed the latest Qt creator using their online install. Cleared the Sigdigger folders, redownloaded the Sigdigger source code from github once more, and still can not successfully build due to lrelease missing....
(I, (at least try to...), use the "develop" tag of SigDigger and the other components).
Do you know if the /usr/lib/qt6/bin/lrelease file is needed and I need to fix my Qt6 install, or is Qt6 looking for lrelease at the wrong path?
— Reply to this email directly, view it on GitHub https://github.com/BatchDrake/SigDigger/issues/262#issuecomment-2495380640, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEVET6QCHIUNKIMYBSNIED2CAUQ5AVCNFSM6AAAAABSKYVZAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVGM4DANRUGA . You are receiving this because you commented.Message ID: @.***>
Oh, I didnt realize I can use the master branch, I just saw the note now after reading your comment above... (I reused my own build scripts from last time I built this some time ago, and didnt notice this had changed).
I will give the master branch a try (on monday)...
Thanks!
