-
Notifications
You must be signed in to change notification settings - Fork 39
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 exclude libraries #108
Comments
Not yet. We'd need to provide an environment variable that supplements the CLI option, and implement it both here and in linuxdeploy. PRs highly welcome! |
Suggested workaround is to call linuxdeploy twice, and remove the offending files once the qt plugin has performed its pass, and then exclude-libraries in the main linuxdeploy app on the second pass. This approach can also be used to add application-specific data files into usr/share. S.
|
FTR PR to fix this linuxdeploy/linuxdeploy#283 |
It would be useful to have the standalone version also able to exclude-libraries, this helps with issues: linuxdeploy#153 linuxdeploy#150 linuxdeploy#110 linuxdeploy#108
It would be useful to have the standalone version also able to exclude-libraries, this helps with issues: linuxdeploy#153 linuxdeploy#150 linuxdeploy#110 linuxdeploy#108
It would be useful to have the standalone version also able to exclude-libraries, this helps with issues: linuxdeploy#153 linuxdeploy#150 linuxdeploy#110 linuxdeploy#108
It would be useful to have the standalone version also able to exclude-libraries, this helps with issues: linuxdeploy#153 linuxdeploy#150 linuxdeploy#110 linuxdeploy#108
It would be useful to have the standalone version also able to exclude-libraries, this helps with issues: linuxdeploy#153 linuxdeploy#150 linuxdeploy#110 linuxdeploy#108
I have a custom Qt installation that contains the debug version of Qt libraries, I didn't find any way to exclude them.
linuxdeploy
has anexclude-library
option but qt plugin hasn't this option.Do you have any way to do that?
The text was updated successfully, but these errors were encountered: