From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Antonin Godard" <antonin.godard@bootlin.com>
Subject: Re: [docs] [PATCH v2 3/4] tools: add gen-doc-links to generate documentation link flags
Date: Fri, 17 Jul 2026 10:38:37 +0200 [thread overview]
Message-ID: <DK0PLBLF0C0D.2L5GC5E385TAL@bootlin.com> (raw)
In-Reply-To: <20260716-gen-doc-links-intersphinx-v2-3-83cb3aef6ff6@bootlin.com>
Hi,
On Thu Jul 16, 2026 at 2:18 PM CEST, Antonin Godard via lists.yoctoproject.org wrote:
[...]
> +def main():
> + args = parse_arguments()
> +
> + yocto_docs_dict = {}
> +
> + if not args.yocto_docs_inv.exists():
> + print(f"yocto-docs inventory not found at {args.yocto_docs_inv}, "
> + "use the --yocto-docs-inv option or set YOCTO_DOCS_INV_PATH "
> + "in your environment")
> + sys.exit(0)
> +
> + if not args.bitbake_inv.exists():
> + print(f"bitbake inventory not found at {args.yocto_docs_inv}, "
> + "use the --bitbake-inv option or set BITBAKE_INV_PATH "
> + "in your environment")
Sorry for the noise, I sent a wrong version of the patch, which shouldn't contain
this but as the script doesn't read doesn't these env variables. The rest of the
patch is the same so I'll delay sending a v3.
Antonin
next prev parent reply other threads:[~2026-07-17 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 12:18 [PATCH v2 0/4] Generate documentation links for OE-Core Antonin Godard
2026-07-16 12:18 ` [PATCH v2 1/4] ref-manual/tasks.rst: convert to glossaries Antonin Godard
2026-07-16 12:18 ` [PATCH v2 2/4] ref-manual/variables.rst: remove flags from variable names Antonin Godard
2026-07-16 12:18 ` [PATCH v2 3/4] tools: add gen-doc-links to generate documentation link flags Antonin Godard
2026-07-17 8:38 ` Antonin Godard [this message]
2026-07-16 12:18 ` [PATCH v2 4/4] .pre-commit-config.yaml: add gen-doc-links Antonin Godard
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=DK0PLBLF0C0D.2L5GC5E385TAL@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.