Skip to content
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

Correctly handle libraries in subdirectories #328

Merged
merged 3 commits into from Nov 10, 2018

Conversation

M-Mueller
Copy link
Contributor

Attempt to fix #327.

I also created a small demo project

@probonopd
Copy link
Owner

probonopd commented Oct 31, 2018

Thanks @M-Mueller for looking into this. Can we do without adding -no-copy-packaged-libs as an option, making it the default behavior?

Can you think of situation where this does not do "the right thing"?

I am always looking to minimize the number of options because linuxdeployqt should "just work" without having to fiddle around.

@M-Mueller
Copy link
Contributor Author

There could be a problem if LD_LIBRARY_PATH points to a folder inside the package. I'm not sure if this is a use-case though, since libraries would end up twice in the final AppImage and increasing the size unnecessarily. I that case the libraries should just be moved to the lib folder before calling linuxdeployqt.

@probonopd probonopd merged commit 3381c6c into probonopd:master Nov 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Correctly handle libraries in subdirectories
2 participants