From: Andreas Ziegler <br025@umbiko.net>
To: buildroot@buildroot.org
Cc: Andreas Ziegler <br025@umbiko.net>
Subject: [Buildroot] [PATCH 2/3] package/mpd: disable build of manuals
Date: Sat, 14 Mar 2026 07:18:34 +0100 [thread overview]
Message-ID: <20260314061837.9425-3-br025@umbiko.net> (raw)
In-Reply-To: <20260314061837.9425-1-br025@umbiko.net>
The documentation feature was introduced with version 0.22, but is not
used. Instead two other options (also introduced with 0.22) control
building HTML manual and man pages. If the tools needed are not found,
the documentation build finishes silently.
Save Meson some effort by setting both options to 'false'.
Signed-off-by: Andreas Ziegler <br025@umbiko.net>
---
package/mpd/mpd.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/mpd/mpd.mk b/package/mpd/mpd.mk
index 3df6276a11..c8107be128 100644
--- a/package/mpd/mpd.mk
+++ b/package/mpd/mpd.mk
@@ -19,6 +19,8 @@ MPD_SELINUX_MODULES = mpd
MPD_CONF_OPTS = \
-Daudiofile=disabled \
-Ddocumentation=disabled \
+ -Dhtml_manual=false \
+ -Dmanpages=false \
-Dmpcdec=disabled \
-Dopenmpt=disabled \
-Dpipewire=disabled \
--
2.53.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-14 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 6:18 [Buildroot] [PATCH 0/3] package/mpd: fix configuration Andreas Ziegler
2026-03-14 6:18 ` [Buildroot] [PATCH 1/3] package/mpd: enforce tcp for options using http Andreas Ziegler
2026-03-21 22:10 ` Julien Olivain via buildroot
2026-03-27 10:02 ` Thomas Perale via buildroot
2026-03-14 6:18 ` Andreas Ziegler [this message]
2026-03-27 10:02 ` [Buildroot] [PATCH 2/3] package/mpd: disable build of manuals Thomas Perale via buildroot
2026-03-14 6:18 ` [Buildroot] [PATCH 3/3] package/mpd: add missing optional dependency Andreas Ziegler
2026-03-27 10:02 ` Thomas Perale via buildroot
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=20260314061837.9425-3-br025@umbiko.net \
--to=br025@umbiko.net \
--cc=buildroot@buildroot.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