From: Clara Kowalsky <clara.kowalsky@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, xenomai@lists.linux.dev
Subject: Re: [PATCH 2/3] docs: Fix a2x warning for PDF builds
Date: Tue, 8 Sep 2026 09:27:10 +0200 [thread overview]
Message-ID: <d508985c-bd9f-4e66-aaf5-5645e5a4f9dd@siemens.com> (raw)
In-Reply-To: <308d85c3-7e7f-40f1-8755-5a99b25d0015@siemens.com>
On 9/7/26 16:22, Jan Kiszka wrote:
> On 03.09.26 10:34, Clara Kowalsky wrote:
>> The documentation PDF build passes "-D" to a2x, raising warnings such
>> as
>>
>> a2x: WARNING: --destination-dir option is only applicable to HTML and manpage based outputs
>>
>> Drop the unsupported option for PDF builds.
>> See #18.
>>
>> Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
>> ---
>> doc/asciidoc/Makefile.am | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/doc/asciidoc/Makefile.am b/doc/asciidoc/Makefile.am
>> index 782c7a23f..669decaeb 100644
>> --- a/doc/asciidoc/Makefile.am
>> +++ b/doc/asciidoc/Makefile.am
>> @@ -91,7 +91,7 @@ html/%: %.adoc Makefile
>> $(A2X) -f manpage -D man1 $(ASCIIDOC_MAN_OPTS) $<
>>
>> %.pdf: %.adoc Makefile
>> - $(A2X) -f pdf -D . $(ASCIIDOC_PDF_OPTS) $<
>> + $(A2X) -f pdf $(ASCIIDOC_PDF_OPTS) $<
>>
>> $(tmpdir)/%.txt: %.adoc Makefile plaintext.conf plaintext.xsl
>> @$(mkdir_p) $(tmpdir)
>
> Could it be that this did have some side effects? My pipeline is red
> because of missing .pdf files:
>
> https://gitlab.com/Xenomai/xenomai3/xenomai-doc/-/jobs/16348492423
>
> Jan
>
Yes. When omitting the -D destination dir, the pdf is placed in the
source dir where the .adoc is located.
https://linux.die.net/man/1/a2x
build/doc/asciidoc$ a2x -f pdf -a icons -a toc -a toclevels=3 -a
xenover=3.3 ../../../doc/asciidoc/MIGRATION.adoc
When using "-D .", the warning is printed that the option is not
supported for pdf outputs, but it actually places the .pdf into the
wanted directory.
As we want the pdfs generated in the build dir, let's omit the commit
and live with the warning.
Clara
next prev parent reply other threads:[~2026-09-08 7:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 8:34 [PATCH 1/3] docs(xeno3): Fix doxygen parsing of COBALT_IMPL_TIME64 wrappers Clara Kowalsky
2026-09-03 8:34 ` [PATCH 2/3] docs: Fix a2x warning for PDF builds Clara Kowalsky
2026-09-07 14:22 ` Jan Kiszka
2026-09-08 7:27 ` Clara Kowalsky [this message]
2026-09-08 7:43 ` Jan Kiszka
2026-09-03 8:34 ` [PATCH 3/3] docs: Match actual return type for RTDM doxygen declarations Clara Kowalsky
2026-09-03 10:53 ` Jan Kiszka
2026-09-03 11:32 ` Clara Kowalsky
2026-09-03 9:48 ` [PATCH 1/3] docs(xeno3): Fix doxygen parsing of COBALT_IMPL_TIME64 wrappers Florian Bezdeka
2026-09-03 10:34 ` Clara Kowalsky
2026-09-03 10:58 ` Jan Kiszka
2026-09-04 6:27 ` Florian Bezdeka
2026-09-04 11:52 ` Clara Kowalsky
2026-09-03 11:17 ` Florian Bezdeka
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=d508985c-bd9f-4e66-aaf5-5645e5a4f9dd@siemens.com \
--to=clara.kowalsky@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@lists.linux.dev \
/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.