From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: Markus Armbruster <armbru@redhat.com>
Subject: [PATCH] docs: adjust for demise of scripts/create_config
Date: Fri, 5 Nov 2021 13:46:56 +0100 [thread overview]
Message-ID: <20211105124656.512471-1-pbonzini@redhat.com> (raw)
The config-host.h, $TARGET-NAME/config-target.h, $TARGET-NAME/config-devices.h files
are now generated by configure_file() rather than scripts/create_config. Adjust
the relevant paragraph in docs/devel/build-system.rst, and take the occasion to
fix a preexisting confusion of *.h vs *.mak.
Reported-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
docs/devel/build-system.rst | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/docs/devel/build-system.rst b/docs/devel/build-system.rst
index 08f49c845d..1a82ce0b9a 100644
--- a/docs/devel/build-system.rst
+++ b/docs/devel/build-system.rst
@@ -463,11 +463,10 @@ Built by Meson:
scripts/make_device_config.sh program, feeding it the
default-configs/$TARGET-NAME file as input.
-``config-host.h``, ``$TARGET-NAME/config-target.h``, ``$TARGET-NAME/config-devices.h``
- These files are used by source code to determine what features
- are enabled. They are generated from the contents of the corresponding
- ``*.h`` files using the scripts/create_config program. This extracts
- relevant variables and formats them as C preprocessor macros.
+``config-host.h``, ``$TARGET_NAME-config-target.h``, ``$TARGET_NAME-config-devices.h``
+ These files are used by source code to determine what features are
+ enabled. They are generated from the contents of the corresponding
+ ``*.mak`` files using Meson's ``configure_file()`` function.
``build.ninja``
The build rules.
--
2.33.1
next reply other threads:[~2021-11-05 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 12:46 Paolo Bonzini [this message]
2021-11-05 13:43 ` [PATCH] docs: adjust for demise of scripts/create_config Markus Armbruster
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=20211105124656.512471-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).