From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 3/4] Makefile: reintroduce REFTABLE_OBJS
Date: Wed, 09 Sep 2026 14:07:20 -0700 [thread overview]
Message-ID: <xmqqmrtqp20n.fsf@gitster.g> (raw)
In-Reply-To: <20260909195006.2179119-4-szeder.dev@gmail.com> ("SZEDER Gábor"'s message of "Wed, 9 Sep 2026 21:50:05 +0200")
SZEDER Gábor <szeder.dev@gmail.com> writes:
> Object files under "reftable/" used to be listed in the REFTABLE_OBJS
> Makefile variable so we could build a static library from them. This
> static library was removed in f3b4c89d59 (make: delete REFTABLE_LIB,
> add reftable to LIB_OBJS, 2025-10-02), along with filling
> REFTALBE_OBJS with object files.
>
> However, the reftable source files are kind of special, because the
> reftable implementation is supposed to be easily includable in other
> projects. Therefore, the reftable source files don't include
> "git-compat-util.h", with the sole exception of the purposefully
> project-specific "reftable/system.c". Consequently, they shouldn't be
> compiled with our precompiled header, as it does include
> "git-compat-util.h".
This is the first mention of "our precompiled header" in this
series, and the first hint that "our precompiled header" would
include "git-compat-util.h". It may probably give us a better
organization to state it upfront at the beginning of the proposed
log message of this commit. It is of secondary importance that once
in the past we used to have REFTABLE_OBJS Makefile variable that
listed some files (but for completely different purposes). How
about explaining it along this line...
The ultimate endgame of this series is to use the precompiled
header facility to speed up compilation, and the plan is to have
Git specific headers including git-compat-util.h precompiled.
The reftable sources are largely designed to be independent from
the Git source proper, and except for reftable/system.c they do
not include <git-compat-util.h>.
Move the object files in the subsystem from the LIB_OBJS to the
REFTABLE_OBJS Makefile variable, so that we can use LIB_OBJS as
list of files compiled with precompiled header files and others
without
... or something like that, perhaps?
next prev parent reply other threads:[~2026-09-09 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 19:50 [PATCH 0/4] make: precompile "git-compat-util.h" SZEDER Gábor
2026-09-09 19:50 ` [PATCH 1/4] Makefile: remove XDIFF_OBJS initialization SZEDER Gábor
2026-09-09 19:50 ` [PATCH 2/4] cmake: remove any "$(*_OBJS)" variables when parsing Makefile for sources SZEDER Gábor
2026-09-09 19:50 ` [PATCH 3/4] Makefile: reintroduce REFTABLE_OBJS SZEDER Gábor
2026-09-09 21:07 ` Junio C Hamano [this message]
2026-09-09 19:50 ` [PATCH 4/4] Makefile: precompile "git-compat-util.h" SZEDER Gábor
2026-09-09 19:57 ` SZEDER Gábor
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=xmqqmrtqp20n.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=szeder.dev@gmail.com \
/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