From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] sim: sh: move some generated source files to built sources
Date: Mon, 2 Jan 2023 22:56:28 -0500 [thread overview]
Message-ID: <20230103035628.21982-1-vapier@gentoo.org> (raw)
This should have been part of the previous commit 80636a54bcfa2bca3dc8f
("sim: build: move generated headers to built sources"), but they were
missed because they're .c files effectively treated as .h files.
---
sim/Makefile.in | 25 ++++++++++++++-----------
sim/sh/local.mk | 8 ++++++--
2 files changed, 20 insertions(+), 13 deletions(-)
diff --git a/sim/sh/local.mk b/sim/sh/local.mk
index 2dc63323e040..8c2ce0da1499 100644
--- a/sim/sh/local.mk
+++ b/sim/sh/local.mk
@@ -24,10 +24,14 @@
noinst_PROGRAMS += %D%/run
+## List all generated headers to help Automake dependency tracking.
+## NB: These .c files are only included by other .c files. They are not
+## compiled individually. Hence they're really "header" files.
+BUILT_SOURCES += \
+ %D%/code.c \
+ %D%/ppi.c
%C%_BUILD_OUTPUTS = \
%D%/gencode$(EXEEXT) \
- %D%/code.c \
- %D%/ppi.c \
%D%/table.c
## This makes sure build tools are available before building the arch-subdirs.
--
2.39.0
reply other threads:[~2023-01-03 3:56 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=20230103035628.21982-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).