summaryrefslogtreecommitdiff
path: root/package/x11r7/xdriver_xf86-video-intel/xdriver_xf86-video-intel-2.4.2-cross-compile.patch
diff options
context:
space:
mode:
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>2009-07-27 15:02:13 +0200
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2009-07-27 15:02:13 +0200
commit314cdcbd2541cae9fb1709831ec67e36508ac793 (patch)
tree7e5f99c6c74abe2e2e805a276825f4e32654dbd5 /package/x11r7/xdriver_xf86-video-intel/xdriver_xf86-video-intel-2.4.2-cross-compile.patch
parent072d89a883c19dc2f69742c65eae7b4cf81b1f63 (diff)
qt: the GUI module requires the network module to work properly
Running a simple Qt GUI application on an embedded systems without QtNetwork installed doesn't work, the dynamic loader complains that QtNetwork is not present. While I'm not a Qt build system expert, it looks like this dependency really exists, since the src/gui/gui.pri file in Qt sources contains the following line: embedded: QT += network Which would mean that the GUI module needs the network module to operate properly. And a few files in src/gui/embedded/ also include some QtNetwork stuff. This isn't really surprising since the Qt QWS mechanism uses communication between processes through a Unix socket. Therefore, we add a dependency on the network module in the GUI module. We use a 'select' dependency here, since it's might not be really obvious to the user that the GUI module requires the network one. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/x11r7/xdriver_xf86-video-intel/xdriver_xf86-video-intel-2.4.2-cross-compile.patch')
0 files changed, 0 insertions, 0 deletions