-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to specify a custom Qt directory? #221
Comments
What happens if you |
Thanks for the reply @probonopd, no, that didn't work, the script still uses the system directory. |
I don't quite remember how we determine this. To be investigated. |
From what I can see here https://github.com/probonopd/go-appimage/blob/master/src/appimagetool/appdirtool.go, first the script searches standard library directories, then dirs specified in /etc/ld.so.conf, and only then LD_LIBRARY_PATH. Perhaps it makes sense to change the order to look at LD_LIBRARY_PATH first? I wasn't able to build the project myself (build instructions in Readme.md seem to be outdated?). |
That might be worth a try indeed.
Do what https://github.com/probonopd/go-appimage/blob/master/.github/workflows/build.yaml does: Essentially, run |
Thanks, it built. So, two things made the script pick up my Qt installation directory:
Perhaps it makes sense to introduce an optional env variable for the Qt installation directory that considers these things. |
When you run your application before using go-appimage, then it picks up the correct Qt, right? We need to find out how that works. Then we can use that information instead of relying on qtPrfxpath, which indeed can be wrong (and often is). |
On Ubuntu 20 the appimage tool picks up qt libs from the system library directory (/usr/lib/x86_64-linux-gnu/qt5) instead of the one used for development ($HOME/Qt/5.15.2/gcc_64/lib).
Is there a way to specify the one located in $HOME, similar to what can be done with a -qmake CLI option (or setting PATH variable to Qt's bin dir) for linuxdeployqt?
The text was updated successfully, but these errors were encountered: