Hi Alex
In order to make hotdoc work for orc and gstreamer1.0, I need to enable
Extensions of hotdoc to work.
So I need to add additional RDEPENDS including: python3-dbus-deviation
python3-networkx python3-cchardet python3-pkgconfig clang llvm
After addind additional RDEPENDS, the RDEPENDS is as following:
RDEPENDS:${PN} += "clang llvm python3-appdirs python3-cchardet
python3-dbus-deviation python3-lxml python3-networkx python3-pkgconfig
python3-pyyaml python3-schema python3-toposort python3-wheezy-template"
Among these RDEPENDS, some OSS do not exist in the OE‑core, I need to add
them newly. Others already exist in meta‑oe, I need to move them from meta‑oe
to OE‑core as following .
Is it okay? If so, I will send the v4 patchsets.
New Added:
python3-dbus-deviation
python3-schema
python3-toposort
python3-wheezy-template
Move from meta-oe:
python3-appdirs
python3-networkx
python3-cchardet
python3-pkgconfig
Liu
________________________________
发件人: Alexander Kanavin <[email protected]>
发送时间: 2026年2月10日 17:41
收件人: Liu, Yiding/刘 乙丁 <[email protected]>
抄送: [email protected]
<[email protected]>
主题: Re: [OE-core][PATCH 6/6] orc: Enable hotdoc to produce doc
On Tue, 10 Feb 2026 at 03:42, Yiding Liu (Fujitsu)
<[email protected]> wrote:
> I try to enable doc in gstreamer1.0-vaapi, gstreamer1.0-plugins-base
> and gstreamer1.0 but found a problem
>
> There is a definition in docs/meson.build which prevent building doc
> in cross building.
>
> if meson.is_cross_build()
> if get_option('doc').enabled()
> error('Documentation enabled but building the doc while cross
> building is not supported yet.')
> endif
>
> message('Documentation not built as building it while cross building is
> not supported yet.')
> subdir_done()
> endif
>
> So what should I do next? Maybe I should send thest patchsets to
> meta-oe?
If you have time to look into gstreamer issues, then you could add a
local patch to gstreamer recipes to remove the above code block, then
set 'doc' to enabled and see what happens (upstream-status doesn't
matter at this point yet). Presumably gstreamer upstream has that
because 'doc' needs running target binaries, but in yocto we have ways
to do it (via qemu). So please try and report, then we'll decide what
to do next.
If you do not have time to do this (which is totally fine), then yes,
hotdoc should be sent to meta-oe in my opinion, because enabling it to
support docs in a single, minor recipe in oe-core does not make sense.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#230946):
https://lists.openembedded.org/g/openembedded-core/message/230946
Mute This Topic: https://lists.openembedded.org/mt/117750589/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
