From: Randy MacLeod <randy.macleod@windriver.com>
To: liuyd.fnst@fujitsu.com
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH v2] orc: upgrade 0.4.41 -> 0.4.42
Date: Mon, 19 Jan 2026 13:50:37 -0500 [thread overview]
Message-ID: <d52e2bbb-5a81-4af5-897f-3811e85d8d46@windriver.com> (raw)
In-Reply-To: <20260114011902.10064-1-liuyd.fnst@fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 3815 bytes --]
On 2026-01-13 8:19 p.m., Yiding Liu (Fujitsu) via lists.openembedded.org
wrote:
> 1.Changelog
> - Initial 64-bit RISC-V support (Maksymilian Knust, Filip Wasil)
> - Add 64-bit LoongArch support (Jin Bo, Hecai Yuan)
> - Implement release and reuse of temporary registers for some targets (Jorge Zapata)
> - x86: Implement EVEX encoding and an opcode validation system (Jorge Zapata)
> - x86: Opcode refactor, improved constant handling and various other fixes (Jorge Zapata)
> - x86: add missing rounding operands for AVX and SSE (L. E. Segovia)
> - x86: Implement 64-bit single move constant load (L. E. Segovia)
> - includes: stop exporting the private compiler and OrcTarget definitions (Jorge Zapata)
> - Use hotdoc instead of gtk-doc to generate the documentation (Jorge Zapata)
> - ORC_DEBUG_FATAL environment variable allows abort on log messages of a certain level (Carlos Falgueras García)
> - Error message improvements and NEON backend clean-ups (Alexander Slobodeniuk)
> - Fix a few valgrind issues (Doug Nazar)
> - Build: enable tools such as orcc and orc-bugreport by default (Nirbheek Chauhan)
> - Various build fixes (L. E. Segovia, Sebastian Dröge)
>
> 2.Documentation are no longer built with gtk_doc,it was replaced by hotdoc.
> https://gitlab.freedesktop.org/gstreamer/orc/-/commit/0ad1f5884c654b614cf1ddd114a7ec9140311a3a
Thanks Yiding!
Most likely this commit will be merged into master this week, based on
today's patch review discussion.
Did you look at the HotDoc system and consider writing a recipe for it?
Only a couple of distros seem to have HotDoc packages so far:
https://pkgs.org/search/?q=hotdoc
but if it's simple enough and going to be used by gstreamer, then an
oe-core recipe might make sense.
I created a YP bugzilla issue to track this idea:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=16144
../Randy
>
> Signed-off-by: Liu Yiding<liuyd.fnst@fujitsu.com>
> ---
> .../recipes-devtools/orc/{orc_0.4.41.bb => orc_0.4.42.bb} | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
> rename meta/recipes-devtools/orc/{orc_0.4.41.bb => orc_0.4.42.bb} (81%)
>
> diff --git a/meta/recipes-devtools/orc/orc_0.4.41.bb b/meta/recipes-devtools/orc/orc_0.4.42.bb
> similarity index 81%
> rename from meta/recipes-devtools/orc/orc_0.4.41.bb
> rename to meta/recipes-devtools/orc/orc_0.4.42.bb
> index 60677577b0..f56b9058c2 100644
> --- a/meta/recipes-devtools/orc/orc_0.4.41.bb
> +++ b/meta/recipes-devtools/orc/orc_0.4.42.bb
> @@ -5,17 +5,13 @@ LICENSE = "BSD-2-Clause & BSD-3-Clause"
> LIC_FILES_CHKSUM ="file://COPYING;md5=1400bd9d09e8af56b9ec982b3d85797e"
>
> SRC_URI ="http://gstreamer.freedesktop.org/src/orc/orc-${PV}.tar.xz"
> -SRC_URI[sha256sum] = "cb1bfd4f655289cd39bc04642d597be9de5427623f0861c1fc19c08d98467fa2"
> +SRC_URI[sha256sum] = "7ec912ab59af3cc97874c456a56a8ae1eec520c385ec447e8a102b2bd122c90c"
>
> -inherit meson pkgconfig gtk-doc
> +inherit meson pkgconfig
>
> # distinguish from apache:orc
> CVE_PRODUCT = "gstreamer:orc"
>
> -GTKDOC_MESON_OPTION = "gtk_doc"
> -GTKDOC_MESON_ENABLE_FLAG = "enabled"
> -GTKDOC_MESON_DISABLE_FLAG = "disabled"
> -
> BBCLASSEXTEND = "native nativesdk"
>
> PACKAGES =+ "orc-examples"
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#229300):https://lists.openembedded.org/g/openembedded-core/message/229300
> Mute This Topic:https://lists.openembedded.org/mt/117254623/3616765
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [randy.macleod@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
# Randy MacLeod
# Wind River Linux
[-- Attachment #2: Type: text/html, Size: 5752 bytes --]
next prev parent reply other threads:[~2026-01-19 18:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 1:19 [OE-core][PATCH v2] orc: upgrade 0.4.41 -> 0.4.42 Liu Yiding
2026-01-19 18:50 ` Randy MacLeod [this message]
2026-01-20 2:58 ` 回复: " Yiding Liu (Fujitsu)
2026-01-20 3:15 ` Patchtest results for " patchtest
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=d52e2bbb-5a81-4af5-897f-3811e85d8d46@windriver.com \
--to=randy.macleod@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=liuyd.fnst@fujitsu.com \
--cc=openembedded-core@lists.openembedded.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