git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
	 Nathan Royce <nroycea+kernel@gmail.com>,
	 git@vger.kernel.org
Subject: Re: FR: Provide Out-Of-Tree Building; Provide Cross-Compile Parameters
Date: Wed, 10 Jul 2024 08:53:29 -0700	[thread overview]
Message-ID: <xmqqfrshz1ja.fsf@gitster.g> (raw)
In-Reply-To: <Zo3-FVT5EFyKsdGc@danh.dev> ("Đoàn Trần Công Danh"'s message of "Wed, 10 Jul 2024 10:20:53 +0700")

Đoàn Trần Công Danh <congdanhqx@gmail.com> writes:

>> ...  And "cross compilation" is
>> one of the things that is so obvious "isn't it nice if we had..."
>> items.  At least the offer has to be a bit more, like "I'll help in
>> this and that area (e.g., organizing the effort, keeping track of
>> progress, researching dependencies, ...).  Any others who want to
>> join forces?"
>
> I thought in Git project, Makefile is the official build system, and
> the autotools build system is only an after-thought, no?

True.  In addition to autotools, there also is cmake "support" (only
meant to be used for Windows) in our tree, which us non-Windows
folks pretty much treat like how Makefile-only folks treat
autotools.

But even if they started as and still are after-thought, with enough
interest by other participant, there is nothing forbidding a
contributor to organize an effort to improve them.  The only
constraint from our side is not to butcher the main build system too
badly to make Makefile-only build less pleasant to work with and
harder to maintain.

Thanks.



      parent reply	other threads:[~2024-07-10 15:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 16:37 FR: Provide Out-Of-Tree Building; Provide Cross-Compile Parameters Nathan Royce
2024-07-08 16:52 ` Eric Sunshine
2024-07-08 18:32   ` Nathan Royce
2024-07-08 19:08     ` Eric Sunshine
2024-07-08 19:56       ` Junio C Hamano
2024-07-10  3:20         ` Đoàn Trần Công Danh
2024-07-10  8:21           ` Nathan Royce
2024-07-10 15:53           ` Junio C Hamano [this message]

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=xmqqfrshz1ja.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=congdanhqx@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nroycea+kernel@gmail.com \
    --cc=sunshine@sunshineco.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;
as well as URLs for NNTP newsgroup(s).