unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brendan Tildesley <mail@brendan.scot>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 43446@debbugs.gnu.org
Subject: bug#43446: Qt Apps cant make use of qtwayland due to QT_PLUGIN_PATH '= wrapping
Date: Mon, 5 Oct 2020 17:39:28 +1100	[thread overview]
Message-ID: <400a2e9e-4d0a-75b5-8288-0e07d515c139@brendan.scot> (raw)
In-Reply-To: <87mu1217s3.fsf@elephly.net>

On 4/10/20 10:43 pm, Ricardo Wurmus wrote:
> 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.
>
Thanks for pointing that out. But, currently a Guix Qt program is unable 
to see plugins available in the environment/profile even if the variable 
is set because the wrapper just deletes that in its local environment. 
It can only see what's in it's inputs. How else can that be fixed?

cat `which nheko`|grep QT;

export 
QT_PLUGIN_PATH="/gnu/store/swqnld90m4gmmc1qaf4lg1psvf6q0rr0-qttools-5.14.2/lib/qt5/plugins:/gnu/store/j0b10r3djln34avx4qxh1kxzg70fn04r-qtbase-5.14.2/lib/qt5/plugins:/gnu/store/lh2yq7dlw3cfaf613h787drpy6f146n3-qtdeclarative-5.14.2/lib/qt5/plugins:/gnu/store/cz6lfbphrdqvgrbhgdq0hd7a50015i5h-qtmultimedia-5.14.2/lib/qt5/plugins:/gnu/store/r4h7w3zw02nc33bi7bjlqbl9b8kilh9r-qtsvg-5.14.2/lib/qt5/plugins"






      reply	other threads:[~2020-10-05  6:40 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 ` bug#43446: Qt Apps cant make use of qtwayland due to QT_PLUGIN_PATH '= wrapping Ricardo Wurmus
2020-10-05  6:39   ` Brendan Tildesley [this message]

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=400a2e9e-4d0a-75b5-8288-0e07d515c139@brendan.scot \
    --to=mail@brendan.scot \
    --cc=43446@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).