Quoting Nikos Chantziaras:
On 16/01/2019 14:46, Roland Hughes wrote:
# Unlike the system directories the RPATH tree isn't walked, only the
actual
# entry. Must list all of them for deployment.
#
QMAKE_RPATHDIR += $ORIGIN/lib: \
$ORIGIN/plugins: \
$ORIGIN/plungins/platforms: \
$ORIGIN/plugins/qtwebengine: \
$ORIGIN/libexec:
You don't need all that. Plugins are loaded dynamically by Qt after the
application has already been loaded. The system loader does not load any
plugins, and so they don't need an rpath.
Shouldn't need all of that. Possibly. When building a single .deb
which would deploy and run on Ubuntu 14.04, 16.04 and 18.04 machines
without any Internet connection, I did. At one point it was even a
multi-arch .deb. One package bringing along everything needed for the
32-bit executables to run on 64-bit machines which did not have the
IA-32 (or whatever they call them these days) packages installed.
--
Roland Hughes, President
Logikal Solutions
(630) 205-1593
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
http://lesedi.us
_______________________________________________
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
