From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH] buildtools/cmdline-gen: add more headers to generated file
Date: Thu, 30 Apr 2026 12:30:53 +0100 [thread overview]
Message-ID: <20260430113053.2397113-1-bruce.richardson@intel.com> (raw)
The generated cmdline header file output often uses uintXX_t types for
parameters specified in the input file. Therefore include stdint.h so
that the types are available for uses of the generated file without
requiring the user to include the header in their C file.
Although not strictly required, also include cmdline_socket.h too, to
provide the "cmdline_stdin_new()" function. The standard cmdline.h only
provides the more generic "cmdline_new()" function, which is less useful
for many cases. Therefore, having the extra header include just makes
things a little easier on the end-user.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
buildtools/dpdk-cmdline-gen.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/buildtools/dpdk-cmdline-gen.py b/buildtools/dpdk-cmdline-gen.py
index 7dadded783..d87adcfca9 100755
--- a/buildtools/dpdk-cmdline-gen.py
+++ b/buildtools/dpdk-cmdline-gen.py
@@ -143,8 +143,11 @@ def process_commands(infile, hfile, cfile, ctxname):
/* File autogenerated by {sys.argv[0]} */
#ifndef GENERATED_COMMANDS_H
#define GENERATED_COMMANDS_H
+
+#include <stdint.h>
#include <rte_common.h>
#include <cmdline.h>
+#include <cmdline_socket.h>
#include <cmdline_parse_string.h>
#include <cmdline_parse_num.h>
#include <cmdline_parse_ipaddr.h>
--
2.51.0
reply other threads:[~2026-04-30 11:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260430113053.2397113-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.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