From: Dariqq <dariqq@posteo.net>
To: 73028@debbugs.gnu.org
Cc: Dariqq <dariqq@posteo.net>,
"Florian Pelz" <pelzflorian@pelzflorian.de>,
"Ludovic Courtès" <ludo@gnu.org>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#73028] [PATCH] doc: Document usage of #:out-of-source? for meson-build-system.
Date: Wed, 4 Sep 2024 16:26:00 +0000 [thread overview]
Message-ID: <f4bd571d1d0753acc003b4f1b371860e45270cce.1725467160.git.dariqq@posteo.net> (raw)
Followup to 220546810830422f8ec3e6a4145fec85429914a1.
* doc/guix.texi (meson-build-system): Document #:out-of-source? parameter.
Change-Id: I730e1aef15010006a68710f8e46ce75dc50e6c67
---
doc/guix.texi | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guix.texi b/doc/guix.texi
index 16c697586a..2302e0f15c 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -10146,6 +10146,10 @@ Build Systems
of inputs, and they can be changed with the parameters @code{#:meson}
and @code{#:ninja} if needed.
+As Meson only supports out-of-source builds the @code{#:out-of-source?}
+parameter specifies whether to search for license files in the source
+or build directory.
+
This build system is an extension of @code{gnu-build-system}, but with the
following phases changed to some specific for Meson:
base-commit: 9a03ab25ba889be27b34d5cebea05d5ac3b0a033
--
2.45.2
next reply other threads:[~2024-09-04 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 16:26 Dariqq [this message]
2024-09-11 6:09 ` [bug#73028] [PATCH] doc: Document usage of #:out-of-source? for meson-build-system Maxim Cournoyer
2024-09-11 15:18 ` Dariqq
2024-09-12 0:56 ` Maxim Cournoyer
2024-09-12 7:12 ` Dariqq
2024-09-12 12:02 ` Maxim Cournoyer
2024-09-12 19:19 ` Dariqq
2024-09-14 13:41 ` Maxim Cournoyer
2024-09-19 14:07 ` Dariqq
2024-09-22 5:57 ` Maxim Cournoyer
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=f4bd571d1d0753acc003b4f1b371860e45270cce.1725467160.git.dariqq@posteo.net \
--to=dariqq@posteo.net \
--cc=73028@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=pelzflorian@pelzflorian.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.