From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: The defs.h / common-defs.h / server.h rule
Date: Fri, 23 Feb 2024 14:06:44 -0700 [thread overview]
Message-ID: <87bk86yjob.fsf@tromey.com> (raw)
In-Reply-To: <88f15917-7989-4e47-a7cf-2cb62faad7ad@polymtl.ca> (Simon Marchi's message of "Fri, 23 Feb 2024 15:35:30 -0500")
Simon> I suppose the other classic way to do this is with an -include flag,
Simon> passed to the compiler?
I don't know if any projects do this, but traditionally it's not done by
GNU-ish programs, I guess because -include was GCC-specific, i.e., not
portable.
Simon> defs.h & co pull in a ton of stuff that is not needed everywhere, so I
Simon> think it would be nice to gradually remove some includes from them, and
Simon> include things where they are really needed. This could help build
Simon> times and avoid recompiling files unnecessarily.
Yeah, that'd be great. gdb's header files are a crazy mess.
Tom
next prev parent reply other threads:[~2024-02-23 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2f2f552a-0028-49cc-adbe-ca038c1e9acd@polymtl.ca>
2024-02-20 12:20 ` Andrew Burgess
2024-02-20 14:52 ` Tom Tromey
2024-02-20 15:14 ` Tom Tromey
2024-02-23 20:35 ` Simon Marchi
2024-02-23 21:06 ` Tom Tromey [this message]
2024-02-23 21:55 ` Simon Marchi
2024-02-27 14:54 ` Tom Tromey
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=87bk86yjob.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).