[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: QT install and search paths
From: |
宋文武 |
Subject: |
Re: QT install and search paths |
Date: |
Sun, 03 Sep 2017 12:58:04 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Hartmut Goebel <address@hidden> writes:
> Am 27.08.2017 um 18:49 schrieb Hartmut Goebel:
>
> It is searched in several sub-directories of
> /tmp/guix-build-…/qtwayland-opensource-src-5.9.1/plugins/platforms/../../../
> (which is the
> /tmp/guix-build-qtwayland-5.9.1.drv-0 directory), but not in …/lib. I did
> not find out how to
>
> Uff, I tracked this down in a heavy thinking session.
>
> * This search-path stems from the libraries RUNPATH, which was
> $ORIGIN/../../lib and is now only $ORIGIN/../../../
>
> * The RUNPATH is set in
> /gnu/store/…-qtbase-5.9.1/lib/qt5/mkspecs/features/qt.prf line 272, using the
> relative path from $$qtRelativeRPathBase (which equals
> $target.path, which is /gnu/store/…-qtbase-5.9.1/lib/qt5/plugins/platforms)
> to $QT_INSTALL_LIBS (which is /gnu/store/…-qtbase-5.9.1/lib). This relative
> path obviously is
> ../../../ .
>
> * Prior to this patch we installed the plugins into …-qtbase-5.9.1/plugins,
> which results in the aforementioned relative path to be ../../lib and the
> RUNPATH to be set to
> $ORIGIN/../../lib.
Oh, that's right, thanks!
>
> Conclusions:
>
> 1. It's been pure luck that the qtwayland tests passed prior to this change.
>
> 2. Do make the tests pass, we need to set LD_LIBRARY_PATH prior to running
> the tests
>
Yeah, patch updated with qtwayland fixed:
0001-gnu-qtbase-Use-a-more-standard-directory-layout.patch
Description: Text Data
> 3. tests of other packages may fail for the same reason.
Yes, I have got tiled running, and find that 'cool-retro-term' need to
be adjusted.
And vlc fails to build due to can't find headers of Qt5X11Extras.
Indeed, the pkg-config output of Qt5X11Extras seems wrong:
--8<---------------cut here---------------start------------->8---
$ pkg-config --cflags --libs Qt5X11Extras
-I/gnu/store/l8xp2i57plmdd3pprhznc8r03ha3sv2s-qtbase-5.9.1/include/qt5/QtGui
-I/gnu/store/l8xp2i57plmdd3pprhznc8r03ha3sv2s-qtbase-5.9.1/include/qt5
-I/gnu/store/l8xp2i57plmdd3pprhznc8r03ha3sv2s-qtbase-5.9.1/include/qt5/QtCore
-I/gnu/store/l8xp2i57plmdd3pprhznc8r03ha3sv2s-qtbase-5.9.1/include/qt5
-I/gnu/store/l8xp2i57plmdd3pprhznc8r03ha3sv2s-qtbase-5.9.1/include/qt5/QtX11Extras
-I/gnu/store/l8xp2i57plmdd3pprhznc8r03ha3sv2s-qtbase-5.9.1/include/qt5
-L/gnu/store/l8xp2i57plmdd3pprhznc8r03ha3sv2s-qtbase-5.9.1/lib -lQt5X11Extras
-lQt5Gui -lQt5Core
--8<---------------cut here---------------end--------------->8---
I can try fix this pkg-config issue.
>
> I'll take care of the packages in kde-frameworks.scm, I assume/hope
> Thomas will take care of the ones in kde.scm.
Yeah, I build 'kiarchive', and find it puts 'mkspecs' under $out, which
needs change to $out/lib/qt5/mkspecs.
>
> 宋文武, how can we coordinate the required changes? Should they go into one
> patch? Or into a series?
I think we could make a series patches, and can squash them later if
suitable.