unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Sergey Trofimov <sarg@sarg.org.ru>
Cc: 46337-done@debbugs.gnu.org
Subject: bug#46337: Attempt to fix the build
Date: Mon, 7 Jun 2021 17:01:06 -0400	[thread overview]
Message-ID: <YL6JEuNVGWQfBcKx@jasmine.lan> (raw)
In-Reply-To: <878s3w5cpz.fsf@sarg.org.ru>

On Sun, May 30, 2021 at 07:54:33PM +0200, Sergey Trofimov wrote:
> 
> Hey there, it seems that qtwebengine build script just lacks the
> `-system-openh264` flag.
> In attempt to fix that I just slap the needed GN arg to the end of
> `src/buildtools/config/linux.pri`
> I've checked that the configure phase succeeds, but the full build takes too
> long on my machine.
> 
> Please find attached the proposed patch.
> 

> From 553a37f4af401f2a53575c0f2d77cb5030344f40 Mon Sep 17 00:00:00 2001
> From: Sergey Trofimov <sarg@sarg.org.ru>
> Date: Sun, 30 May 2021 14:39:15 +0200
> Subject: [PATCH] qtwebengine with openh264

Thanks! I wrote a commit message and pushed as
68dcdf6ea76cddc4f9e53aabe7c1a5724d5508b2




  reply	other threads:[~2021-06-07 21:02 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
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   ` Leo Famulari [this message]
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=YL6JEuNVGWQfBcKx@jasmine.lan \
    --to=leo@famulari.name \
    --cc=46337-done@debbugs.gnu.org \
    --cc=sarg@sarg.org.ru \
    /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).