From: ifreund <ifreund@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] chromium: enable pipewire webrtc backend
Date: Sat, 23 May 2020 11:51:04 +0200 [thread overview]
Message-ID: <20200523095104.LNuHguBN9XFbzkMAlFrrraCC80zPnwefBGci2fMQDc4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22222@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
There is an updated pull request by ifreund against master on the void-packages repository
https://github.com/ifreund/void-packages chromium-enable-pipewire
https://github.com/void-linux/void-packages/pull/22222
chromium: enable pipewire webrtc backend
This allows for webrtc screensharing with, for example, https://github.com/emersion/xdg-desktop-portal-wlr to work.
A patch file from https://github.com/void-linux/void-packages/pull/22222.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-chromium-enable-pipewire-22222.patch --]
[-- Type: text/x-diff, Size: 1618 bytes --]
From 1954d4b9f1ee858e98ecb0d6dbfb258278623074 Mon Sep 17 00:00:00 2001
From: Isaac Freund <ifreund@ifreund.xyz>
Date: Sat, 23 May 2020 11:32:49 +0200
Subject: [PATCH] chromium: enable pipewire webrtc backend
This allows for webrtc-based screensharing using, for example,
https://github.com/emersion/xdg-desktop-portal-wlr.
---
srcpkgs/chromium/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/chromium/template b/srcpkgs/chromium/template
index 8775ca32284..cee3d182273 100644
--- a/srcpkgs/chromium/template
+++ b/srcpkgs/chromium/template
@@ -2,7 +2,7 @@
pkgname=chromium
# See http://www.chromium.org/developers/calendar for the latest version
version=83.0.4103.61
-revision=1
+revision=2
archs="i686 x86_64*"
short_desc="Google's attempt at creating a safer, faster, and more stable browser"
maintainer="Enno Boland <gottox@voidlinux.org>"
@@ -31,7 +31,7 @@ makedepends="libpng-devel gtk+-devel gtk+3-devel nss-devel pciutils-devel
libjpeg-turbo-devel libevent-devel json-c-devel harfbuzz-devel
minizip-devel jsoncpp-devel zlib-devel libcap-devel libXdamage-devel
re2-devel fontconfig-devel freetype-devel opus-devel
- ffmpeg-devel libva-devel python-setuptools"
+ ffmpeg-devel libva-devel python-setuptools pipewire-devel"
depends="libexif hwids desktop-file-utils hicolor-icon-theme xdg-utils"
build_options_default="clang"
@@ -164,8 +164,9 @@ do_configure() {
'enable_widevine=true'
'enable_hangout_services_extension=true'
'is_desktop_linux=true'
+ 'rtc_use_pipewire=true'
)
-
+
conf+=(
"use_vaapi=$(vopt_if vaapi true false)"
)
next prev parent reply other threads:[~2020-05-23 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 9:34 [PR PATCH] " ifreund
2020-05-23 9:51 ` ifreund [this message]
2020-05-23 15:46 ` ifreund
2020-05-23 15:46 ` [PR PATCH] [Closed]: " ifreund
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=20200523095104.LNuHguBN9XFbzkMAlFrrraCC80zPnwefBGci2fMQDc4@z \
--to=ifreund@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).