unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: pkill9 <pkill9@runbox.com>
Cc: 46337@debbugs.gnu.org
Subject: [bug#46337] A patch to enable building proprietary codecs in qtwebengine
Date: Sun, 7 Feb 2021 13:12:12 -0500	[thread overview]
Message-ID: <YCAtfGuZDUrjAHwx@jasmine.lan> (raw)
In-Reply-To: <20210206014748.5b281d65@runbox.com>

On Sat, Feb 06, 2021 at 01:47:48AM +0000, pkill9 wrote:
> diff --git a/gnu/packages/qt.scm b/gnu/packages/qt.scm
> index 4fbb157600..057644a576 100644
> --- a/gnu/packages/qt.scm
> +++ b/gnu/packages/qt.scm
> @@ -1939,7 +1939,8 @@ using the Enchant spell-checking library.")
>                         "--webengine-printing-and-pdf=no"
>                         "--webengine-ffmpeg=system"
>                         "--webengine-icu=system"
> -                       "--webengine-pepper-plugins=no")))))
> +                       "--webengine-pepper-plugins=no"
> +		       "-webengine-proprietary-codecs")))))

Thanks! I tried building with this flag on a powerful computer, but the
build failed because it couldn't find the dependency openh264. That is
packaged, so we just need an updated patch.




  parent reply	other threads:[~2021-02-07 18:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06  1:47 [bug#46337] A patch to enable building proprietary codecs in qtwebengine pkill9
2021-02-06 10:10 ` Tobias Geerinckx-Rice via Guix-patches via
2021-02-06 13:05   ` Tobias Geerinckx-Rice via Guix-patches via
2021-02-07 18:12 ` Leo Famulari [this message]
2021-02-08 15:40   ` pkill9
2021-02-08 16:36     ` Leo Famulari
2021-02-08 22:53       ` pkill9
2021-02-08 23:44         ` pkill9
2021-02-09 21:17           ` Leo Famulari
2021-05-30 17:54 ` [bug#46337] Attempt to fix the build Sergey Trofimov
2021-06-07 21:01   ` bug#46337: " Leo Famulari
2021-05-30 18:47 ` [bug#46337] Clarification for the previous patch Sergey Trofimov
2021-05-30 20:00 ` [bug#46337] Update Sergey Trofimov

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=YCAtfGuZDUrjAHwx@jasmine.lan \
    --to=leo@famulari.name \
    --cc=46337@debbugs.gnu.org \
    --cc=pkill9@runbox.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 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).