public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: build against noopenh264 for fedora >=40
Date: Fri, 07 Aug 2026 16:06:30 GMT [thread overview]
Message-ID: <178611879048.1.17633491084894946194.rpms-chromium-16fc415c9d75@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 16fc415c9d758b6425afa62396ac2824a7b02124
Author : Than Ngo <than@redhat.com>
Date : 2024-05-30T10:58:09+02:00
Stats : +21/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/16fc415c9d758b6425afa62396ac2824a7b02124?branch=epel9-next
Log:
build against noopenh264 for fedora >=40
---
diff --git a/chromium.spec b/chromium.spec
index f948062..d4c3e97 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -99,6 +99,10 @@
%endif
%endif
+%if 0%{?fedora} >= 40
+%global noopenh264 1
+%endif
+
# Workaround for https://bugzilla.redhat.com/show_bug.cgi?id=2239523
# Disable BTI until this is fixed upstream.
%global disable_bti 0
@@ -312,7 +316,7 @@
Name: chromium%{chromium_channel}
Version: 125.0.6422.112
-Release: 2%{?dist}
+Release: 3%{?dist}
Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
Url: http://www.chromium.org/Home
License: BSD-3-Clause AND LGPL-2.1-or-later AND Apache-2.0 AND IJG AND MIT AND GPL-2.0-or-later AND ISC AND OpenSSL AND (MPL-1.1 OR GPL-2.0-only OR LGPL-2.0-only)
@@ -651,6 +655,10 @@ Conflicts: ffmpeg-libs%{_isa} < 6.0.1-2
%endif
%endif
+%if 0%{?noopenh264}
+BuildRequires: pkgconfig(openh264)
+%endif
+
# build with system libaom
%if ! %{bundlelibaom}
BuildRequires: libaom-devel
@@ -1542,8 +1550,14 @@ CHROMIUM_BROWSER_GN_DEFINES+=' ffmpeg_branding="Chrome" proprietary_codecs=true
%else
CHROMIUM_BROWSER_GN_DEFINES+=' ffmpeg_branding="Chromium" proprietary_codecs=false is_component_ffmpeg=false enable_ffmpeg_video_decoders=false media_use_ffmpeg=true'
%endif
+# link against noopenh264 library
+%if 0%{?noopenh264}
+CHROMIUM_BROWSER_GN_DEFINES+=' media_use_openh264=true'
+CHROMIUM_BROWSER_GN_DEFINES+=' rtc_use_h264=true'
+%else
CHROMIUM_BROWSER_GN_DEFINES+=' media_use_openh264=false'
CHROMIUM_BROWSER_GN_DEFINES+=' rtc_use_h264=false'
+%endif
CHROMIUM_BROWSER_GN_DEFINES+=' use_kerberos=true'
%if %{use_qt}
@@ -1702,6 +1716,9 @@ system_libs=()
%if ! %{bundleflac}
system_libs+=(flac)
%endif
+%if 0%{?noopenh264}
+ system_libs+=(openh264)
+%endif
build/linux/unbundle/replace_gn_files.py --system-libraries ${system_libs[@]}
@@ -2110,6 +2127,9 @@ getent group chrome-remote-desktop >/dev/null || groupadd -r chrome-remote-deskt
%endif
%changelog
+* Wed May 29 2024 Than Ngo <than@redhat.com> - 125.0.6422.112-3
+- build against noopenh264
+
* Tue May 28 2024 Than Ngo <than@redhat.com> - 125.0.6422.112-2
- Workaround for build error on pp64le
reply other threads:[~2026-08-07 16:06 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178611879048.1.17633491084894946194.rpms-chromium-16fc415c9d75@fedoraproject.org \
--to=than@redhat.com \
--cc=git-commits@fedoraproject.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