orc: Enable hotdoc to produce doc
PATCH v2 1/1 orc: Enable hotdoc to produce doc
Add do_install:append function to fix QA Issue like "File /usr/share/doc/orc/html/assets/js/search/hotdoc_fragments/orctarget.html-enum (unnamed at /work/x86-64-v3-poky-linux/orc/0.4.42/sources/orc-0.4.42/orc/orctarget.h:39:1).fragment in package orc-doc contains reference to TMPDIR [buildpaths]"
--- meta/recipes-devtools/orc/orc_0.4.42.bb | 13 +++++++++++++ 1 file changed, 13 insertions(+)
meta/recipes-devtools/orc/orc_0.4.42.bb +13 -0
@@ -9,6 +9,9 @@ SRC_URI[sha256sum] = "7ec912ab59af3cc97874c456a56a8ae1eec520c385ec447e8a102b2bd1 inherit meson pkgconfig +PACKAGECONFIG ??= "" +PACKAGECONFIG[hotdoc] = ",,hotdoc-native" + # distinguish from apache:orc CVE_PRODUCT = "gstreamer:orc"
@@ -27,3 +30,13 @@ python populate_packages:prepend () { do_compile:prepend:class-native () { sed -i -e 's#/tmp#.#g' ${S}/orc/orccodemem.c } + +#Add this function to deal with QA Issue like File /usr/share/doc/orc/html/assets/js/search/hotdoc_fragments/orctarget.html-enum (unnamed at /work/x86-64-v3-poky-linux/orc/0.4.42/sources/orc-0.4.42/orc/orctarget.h:39:1).fragment in package orc-doc contains reference to TMPDIR [buildpaths] +do_install:append:class-target () { + if ${@bb.utils.contains('PACKAGECONFIG', 'hotdoc', 'true', 'false', d)}; then + rm -rf ${D}${docdir}/${PN}/html/assets/js/search/hotdoc_fragments/*unnamed* + for ss in $(find ${D}${docdir}/${PN}/html -type f); do + sed -i 's,${S},,g' "$ss" + done + fi +}
Signature · 1 line
2.43.0
Quoted 1 line · Yiding Liu (Fujitsu) via lists.openembedded.org
+PACKAGECONFIG[hotdoc] = ",,hotdoc-native"
There's actually a build option called 'hotdoc', to control whether docs are built or not. So it should be used to ensure build determinism and reproducibility, as otherwise this is a floating feature that gets enabled (or not) depending on whether hotdoc-native is in sysroot.
Alex
Quoted 1 line · Alexander Kanavin via lists.openembedded.org
+PACKAGECONFIG[hotdoc] = ",,hotdoc-native"
Maybe call it PACKAGECONFIG[manpages] so that it could be enabled/disabled with the 'api-documentation' DISTRO_FEATURE ?
Quoted 5 lines · Markus Volk via lists.openembedded.org
On Mon, Mar 9 2026 at 18:23:07 +01:00:00, Alexander Kanavin via lists.openembedded.org <[email protected]> wrote:
+PACKAGECONFIG[hotdoc] = ",,hotdoc-native"
Maybe call it PACKAGECONFIG[manpages] so that it could be enabled/disabled with the 'api-documentation'DISTRO_FEATURE?
This option isn't actually generating man pages. It would also require hotdoc recipe in oe-core which at present we decided not to do.
Alex
HI Alex
How about change this line
> +PACKAGECONFIG[hotdoc] = ",,hotdoc-native"
to
PACKAGECONFIG[hotdoc] = "-Dhotdoc=enabled,-Dhotdoc=disabled,hotdoc-native"
Liu
________________________________
发件人: Alexander Kanavin <[email protected]>
发送时间: 2026年3月10日 01:23
收件人: Liu, Yiding/刘 乙丁 <[email protected]>
抄送: [email protected] <[email protected]>; Ross Burton <[email protected]>; Richard Purdie <[email protected]> 主题: Re: [OE-core][PATCH v2] orc: Enable hotdoc to produce doc
Quoted 1 line · Yiding Liu (Fujitsu) via lists.openembedded.org
+PACKAGECONFIG[hotdoc] = ",,hotdoc-native"
There's actually a build option called 'hotdoc', to control whether docs are built or not. So it should be used to ensure build determinism and reproducibility, as otherwise this is a floating feature that gets enabled (or not) depending on whether hotdoc-native is in sysroot.
Alex
Quoted 4 lines · Yiding Liu (Fujitsu)
How about change this line
> +PACKAGECONFIG[hotdoc] = ",,hotdoc-native"
to
PACKAGECONFIG[hotdoc] = "-Dhotdoc=enabled,-Dhotdoc=disabled,hotdoc-native"
Yes, this should be fine.
Alex