[Development] Change in qt/qtbase[5.8]: utilize configure results better in native builds
René J.V. Bertin
rjvbertin at gmail.com
Mon Jan 23 10:56:27 CET 2017
Is it possible that the failure (below) finding the QPA plugin in the test set-up below is a result of this proposed change, somehow?
Or am I overlooking an error in the env. settings to load the required binaries from the testing location?
Qt5 5.8.0RC built with the patch from https://codereview.qt-project.org/182877 was installed with INSTALL_ROOT=/opt/local/testing
Can it be that this difference between Qt5Core.so and Qt5gui.so has something to do with it (all other libraries use $ORIGIN too)?
%> objdump -p /opt/local/testing/libexec/qt5/lib/libQt5Core.so | fgrep PATH
%> objdump -p /opt/local/testing/libexec/qt5/lib/libQt5Gui.so | fgrep PATH
%> env LD_LIBRARY_PATH=/opt/local/testing/libexec/qt5/lib QT_PLUGIN_PATH=/opt/local/testing/share/qt5/plugins QT_QPA_PLATFORM_PLUGIN_PATH=/opt/local/testing/share/qt5/plugins/platforms systray-qt5/systray-qt5
This application failed to start because it could not find or load the Qt platform plugin "xcb"
Available platform plugins are: wayland-org.kde.kwin.qpa, eglfs, linuxfb, minimal, minimalegl, offscreen, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Reinstalling the application may fix this problem.
Abort (core dumped)
More information about the Development