From: Ricardo Wurmus <rekado@elephly.net>
To: Brendan Tildesley <mail@brendan.scot>
Cc: 43446@debbugs.gnu.org
Subject: bug#43446: Qt Apps cant make use of qtwayland due to QT_PLUGIN_PATH '= wrapping
Date: Sun, 04 Oct 2020 14:43:08 +0200 [thread overview]
Message-ID: <87mu1217s3.fsf@elephly.net> (raw)
In-Reply-To: <650d1848-7dc8-2063-265c-1a965a1dd5ee@brendan.scot>
Brendan Tildesley <mail@brendan.scot> writes:
> qt-build-system wraps variables such as QT_PLUGIN_PATH with '=
> instead of prefix, so when qtwayland is installed in a profile or
> included in the environment, the application fails to see it. Programs
> run with export QT_QPA_PLATFORM=wayland-egl will fail to launch.
>
> We could:
>
> 1. Use 'prefix so that the parent environment's variables are appended
> and users have to manually install qtwayland them selves.
> 2. Include qtwayland as an input to every qt package somehow. Can the
> build system do that? Considering that Wayland seems to be the
> future, I feel that Qt GUI applications should support it by
> default. I mean, wayland is in the closure of qtbase anyway.
> 3. Both? Why is '= used anyway?
I can’t say why the Qt build system does this, but in other cases we
know that 'prefix causes problems because the application may end up
loading incompatible binaries leading to a crash. That’s especially the
case on foreign distros, e.g. when the Guix-installed graphical
application loads a plugin from the system’s XDG_* directories.
--
Ricardo
next prev parent reply other threads:[~2020-10-04 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 11:16 bug#43446: Qt Apps cant make use of qtwayland due to QT_PLUGIN_PATH '= wrapping Brendan Tildesley
2020-10-04 10:46 ` bug#43446: EGL-Wayland Raghav Gururajan
2020-10-04 11:23 ` bug#43446: [PATCH] guix: qt-build-system: Fix search-path wrapping Brendan Tildesley
2020-10-04 12:43 ` Ricardo Wurmus [this message]
2020-10-05 6:39 ` bug#43446: Qt Apps cant make use of qtwayland due to QT_PLUGIN_PATH '= wrapping Brendan Tildesley
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mu1217s3.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=43446@debbugs.gnu.org \
--cc=mail@brendan.scot \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).