Additional check to make sure that the undocumented, unsupported and not recommended `-unsupported-allow-new-glibc` option is not abused to create results that are broken; see https://github.com/probonopd/linuxdeployqt/issues/340 for more information
If linuxdeployqt is called with the option -updateinformation=<update
string>, it passes that update string to appimagetool. Otherwise it uses
-g to guess (the original behavior).
Had to move the parsing of -show-exclude-lib up to the block where the
version options are parsed, otherwise a call like
./linuxdeployqt<...>.AppImage -show-exclude-libs
wouldn't work.
CC @patrickelectric
See https://github.com/probonopd/linuxdeployqt/issues/256#issuecomment-373916136
The argument parser requires flags expecting a payload to be passed in
the form -arg=payload. If not, it fails to recognize them and falsely
reports "argument must not start with --". These usability issues
should be gone with these two minor changes.
This helps us avoid pesky libraries which are optional by the main
binary but may be dragged in by some other libraries like
https://github.com/probonopd/linuxdeployqt/issues/235
Usage: -exclude-libs=libqsqlibase,libqsqlodbc,libqsqlpsql,libqsqltds
Also introduces a hint for users about the single quote parameters this
tool provides, most other CLI tools use double quotes for
non-single-char parameters.
Added posibility for developer to deploy aditional Qt plugins through a
list of plugins directories and plugins, relative path to the Qt plugins
directory
and issue a proper error message if not.
When using linuxdeployqt for example in OBS and packages can not
be installed, it can happen that the desktop file is not existing.
This error message makes debugging easier.
Refactor the project structure to make it build as a "Qt module". It's a first step to get this tool closer to Qt.
The main advantage here is: Simply running:
```
qmake
make
make install
```
will compile and install the tool into your Qt installation, and make it a part of your Qt just like any other tool (qmake, etc.)
This change adds a new command line option `qmake` to the tool which
allows the user to specify the qmake executable to be used. By default,
if that option is omitted, the behavior is unchanged (i.e. the tool first
searches for the `qmake` executable and - if this is not successful -
then for either `qmake-qt5` or `qmake-qt4`. If the new option is used,
no search takes place and instead the executable provided is used as-is.
This implements a part of the functionality as discussed in issue #94.
probonopd
tilya
Ilya Bizyaev
Florian Märkl
TheAssassin
Patrick José Pereira
Dinesh Manajipet
TheAssassin
Verban Adrian
Chris Rizzitello
Klaas Freitag
Felix Barz
Martin Höher