From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Junio C Hamano <gitster@pobox.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 10:20:53 +0700 [thread overview]
Message-ID: <Zo3-FVT5EFyKsdGc@danh.dev> (raw)
In-Reply-To: <xmqqjzhvejye.fsf@gitster.g>
On 2024-07-08 12:56:41-0700, Junio C Hamano <gitster@pobox.com> wrote:
> Eric Sunshine <sunshine@sunshineco.com> writes:
>
> >> I'd still suggest and prefer that git (and zlib) follows what others
> >> have settled on doing to be cross-compile-friendly.
> >
> > I can't speak for the zlib project, but for this to happen in Git,
> > someone with an interest in seeing such an outcome will need to submit
> > patches.
>
> Sure.
>
> Somebody unknown to the community suddenly coming here and
> suggesting a feature alone would not achieve anything. If there
> were infinite engineering resources and motivated contributors, and
> if sufficient number of contributors thought something is worth
> doing, it would already have been done. 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?
For cross-compilation, I think various project has been
cross-compiling Git from forever. They only need to provide a file
named `config.mak' with proper information for that platform, e.g:
cat <<-EOF
prefix = /usr
CC = $CC
CFLAGS = $CFLAGS
LDFLAGS = $LDFLAGS
USE_LIBPCRE2 := $(if true; then echo Yes; fi)
perllibdir=/usr/share/perl5/vendor_perl
HOST_CPU = $(config.guess | cut -d- -f1)
ICONV_OMITS_BOM = Yes
NO_REGEX = Yes
EOF
Those last values need to be specified manually because they can't be
detected by running a test program anyway. Those keys are already
listed in Makefile.
--
Danh
next prev parent reply other threads:[~2024-07-10 3:20 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 [this message]
2024-07-10 8:21 ` Nathan Royce
2024-07-10 15:53 ` Junio C Hamano
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=Zo3-FVT5EFyKsdGc@danh.dev \
--to=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).