all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: iyzsong@member.fsf.org (宋文武)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 31668@debbugs.gnu.org
Subject: [bug#31668] [PATCH 2/2] gnu: Add qtwebglplugin.
Date: Mon, 11 Jun 2018 20:19:32 +0800	[thread overview]
Message-ID: <87bmchwm5n.fsf@member.fsf.org> (raw)
In-Reply-To: <6618ca63-034f-b328-2368-3a5679184aee@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 10 Jun 2018 20:03:50 +0200")

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> Am 10.06.2018 um 04:55 schrieb 宋文武:
>> Hello, what’s “implemented badly” means?  I think ‘mesa’ and
>> ‘qtwebsockets’ belongs to the ‘inputs’ nicely, since after build
>> ‘qtwebglplugin’ does keep references to them.
>
> If you put these two into "inputs", the build fails. I can not remember
> the details, but ASAIR it looked like somebody missed preparation. You
> may want to try yourself, qtwebglplugin build quickly.

Oh, that’s due to the package inherit from ‘qtsvg’, and in the inherited
‘configure-qmake’ phase, it will run ‘(assoc-ref inputs "qtbase")’.  Add
‘qtbase’ to ‘inputs’ will make it built, and the ‘perl’ is not needed,
as the below works for me:
--8<---------------cut here---------------start------------->8---
    (native-inputs '())
    (inputs
     `(("mesa" ,mesa)
       ("qtbase" ,qtbase)
       ("qtwebsockets" ,qtwebsockets)))
--8<---------------cut here---------------end--------------->8---

Otherwise, look good to me, thanks!

  reply	other threads:[~2018-06-11 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 13:53 [bug#31668] [PATCH 1/2] gnu: Add qtwebview Hartmut Goebel
2018-05-31 13:54 ` [bug#31668] [PATCH 2/2] gnu: Add qtwebglplugin Hartmut Goebel
2018-06-10  2:55   ` 宋文武
2018-06-10 18:03     ` Hartmut Goebel
2018-06-11 12:19       ` 宋文武 [this message]
2018-06-12 20:49         ` bug#31668: " 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=87bmchwm5n.fsf@member.fsf.org \
    --to=iyzsong@member.fsf.org \
    --cc=31668@debbugs.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.