unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Guix-devel <guix-devel@gnu.org>
Subject: libexec dir and Qt / qtwebengine fails finding QtWebEngineProcess
Date: Fri, 11 Oct 2024 14:53:04 +0200	[thread overview]
Message-ID: <ef2dcc2f-b0c6-4f04-88be-e27b9bb1ae9b@crazy-compilers.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

Hi,

I just built XRview https://codeberg.org/openKMU/xrechnung/ a QT viewer 
for German electronic invoices. This uses qtwebengine to display convert 
and the data.

This fails finding the QtWebEngineProcess executable.

The following paths were searched for Qt WebEngine Process:
  /gnu/store/nns96pk4bsyihmw6yksghglm19nimd9r-qtbase-6.6.3/lib/qt6/libexec/QtWebEngineP
rocess
  /gnu/store/nns96pk4bsyihmw6yksghglm19nimd9r-qtbase-6.6.3/bin/QtWebEngineProcess
  /gnu/store/dq55b09vcw4cwgwivlcrsi0yn3nhv48w-xrview-1.0/bin/QtWebEngineProcess
but could not find it.
You may override the default search path by using 
QTWEBENGINEPROCESS_PATH environment v
ariable.

 From Guix POV the cause is that the libexec directory only from qtbase 
is in this search path.

The message also suggests a simple solution: add native search path 
QTWEBENGINEPROCESS_PATH.

Anyhow this is is not a good solution IMHO, since

  * this will create a long path in QTWEBENGINEPROCESS_PATH while only a
    single entry would suffice
  * this will fail for other parts of Qt also searching the libexec
    directory.

A better solution would be to create a native-search-path (e.g. 
GUIX_QT_LIBEXEC_PATH) and make Qt search this path.

Any idea how we could achieve this?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          |h.goebel@crazy-compilers.com                |
|www.crazy-compilers.com  | compilers which you thought are impossible |

[-- Attachment #2: Type: text/html, Size: 2316 bytes --]

                 reply	other threads:[~2024-10-11 17:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ef2dcc2f-b0c6-4f04-88be-e27b9bb1ae9b@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    /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).