You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the .pro file assumes that the binary is named lrelease-qt5 on non-macOS Unix-like systems, and lrelease elsewhere. Though I have lrelease binary in the qttools5-dev-tools package from Debian Bullseye. Is the condition not clarified enough, or maybe outdated then?
Actually, I guess that the best strategy would be to check for both variants, and use whatever is present in the system, rather than try to deduce it from unrelated parameters like the platform.
The text was updated successfully, but these errors were encountered:
Also on my system lrelease is placed in /usr/lib64/qt5/bin/lrelease
It don't work with both lrelease and lrelease-qt5. I was able to compile the programm only with full path.
Currently, the .pro file assumes that the binary is named
lrelease-qt5
on non-macOS Unix-like systems, andlrelease
elsewhere. Though I havelrelease
binary in theqttools5-dev-tools
package from Debian Bullseye. Is the condition not clarified enough, or maybe outdated then?Actually, I guess that the best strategy would be to check for both variants, and use whatever is present in the system, rather than try to deduce it from unrelated parameters like the platform.
The text was updated successfully, but these errors were encountered: