From: iyzsong@member.fsf.org (宋文武)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: QT install and search paths
Date: Thu, 24 Aug 2017 19:59:30 +0800 [thread overview]
Message-ID: <874lsxi3bx.fsf@member.fsf.org> (raw)
In-Reply-To: <42cac0e9-d948-3ea1-7312-d003751fd6a8@crazy-compilers.com> (Hartmut Goebel's message of "Wed, 23 Aug 2017 20:25:10 +0200")
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> Hi,
>
> I'm currently working on the build of KDE's plasma-desktop. When strac-ing the tets, I dicoverd that plaugins are searched in
>
> /gnu/store/…-qtbase-5.9.1/plugins/…
>
> while most of the KDE program use
>
> /gnu/store/…-plasma-workspace-5.10.4/lib/plugins/… (mind the additional `lib`)
>
> which is not searched. Wondering why, I found this in qt.scm (qtbase):
>
> (search-path-specification
> (variable "QT_PLUGIN_PATH")
> (files '("plugins")))
>
> This means that `lib/plugins` is *not* included in QT_PLUGIN_PATH and thus not searched. (Which I assume is the reason for many test-failures.)
>
> Also in qt.scm (qtbase) there is:
>
> (substitute* qt_config.prf
> …
> (("\$\$\[QT_INSTALL_PLUGINS\]")
> "$$replace(dir, mkspecs/modules, plugins)")
>
> I assume this should make the plugins to be in stalled in …/plugins,
Yes, 'dir' would be $out/mkspecs/modules, this will make a qmake based
package install its Qt plugins into $out/plugins.
> but KDE framework is installing into …/lib/plugins.
>
> So I assume this is wrong or there are other places which need to be adpoted to the changed directory layout.
>
> What do you think?
Currently, it doesn't follow a normal package layout, We should change
it to (like it in Debian and ArchLinux):
ARCHDATA: lib/qt
DATA: share/qt
DOCS: share/doc/qt
HEADERS: include/qt
LIBS: lib
PLUGINS: lib/qt/plugins
LIBEXECS: lib/qt/libexec
BINS: bin
IMPORTS: lib/qt/imports
QML: lib/qt/qml
EXAMPLES: share/doc/qt/examples
Which need adjust the configure flags, search-patchs and the
qt_config.prf of our qtbase package (and maybe some kde ones, I don't
know).
next prev parent reply other threads:[~2017-08-24 11:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 18:25 QT install and search paths Hartmut Goebel
2017-08-24 11:37 ` Thomas Danckaert
2017-08-25 7:32 ` Hartmut Goebel
2017-08-24 11:59 ` 宋文武 [this message]
2017-08-25 7:06 ` Hartmut Goebel
2017-08-25 12:40 ` 宋文武
2017-08-25 16:04 ` 宋文武
2017-08-26 8:31 ` Hartmut Goebel
2017-08-27 16:49 ` Hartmut Goebel
2017-09-02 16:40 ` Hartmut Goebel
2017-09-03 4:58 ` 宋文武
2017-09-03 11:46 ` 宋文武
2017-09-03 12:39 ` Hartmut Goebel
2017-09-03 14:04 ` Hartmut Goebel
2017-09-03 14:46 ` 宋文武
2017-09-04 7:44 ` Thomas Danckaert
2017-09-04 9:16 ` Hartmut Goebel
2017-09-07 13:38 ` 宋文武
2017-09-19 16:30 ` Hartmut Goebel
2017-09-22 12:59 ` Hartmut Goebel
2017-10-06 12:22 ` Hartmut Goebel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lsxi3bx.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.