From: Paul Smith <paul@mad-scientist.net>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: ./configure fails to link test program due to missing dependencies
Date: Wed, 25 Sep 2024 11:33:28 -0400 [thread overview]
Message-ID: <5bd2f41c92a00f7799bc543e229b16fa7a473760.camel@mad-scientist.net> (raw)
In-Reply-To: <xmqqwmj1t0hp.fsf@gitster.g>
On Tue, 2024-09-24 at 10:39 -0700, Junio C Hamano wrote:
> Our dependance of heavy use of GNU-ism in our Makefiles makes an
> argument that make is the common denominator a fairly weak one, so
> the single one that eventually we use does not have to be "make",
> but it has to be something available widely and easy to learn.
Regardless of what one might imagine :), I am not advocating GNU Make
as the perfect solution: it certainly has downsides and disadvantages.
But, it also has benefits that should not be ignored: for example, it's
highly portable and it consists of a single binary that can be copied
anywhere and run from anywhere with no other prerequisites or need for
any setup or privileges. Also it's extremely flexible since it just
runs shell scripts. That also makes portability much more "do it
yourself" than other tools of course.
Meson is portable, but that's because it's written in Python: that
means you have to have a Python interpreter already available
(currently Python 3.7 or better), and the ability to add new modules to
it. Admittedly this is not a super-high bar in 2024, but it's a non-
trivial requirement if you're trying to start from scratch.
Things like cmake provide abstractions that can make building code
simple, but it can be surprisingly difficult to get them to perform
more advanced tricks like generating source files, linker map files,
etc. It can be done, but it's... not always easy. And it has some
weird behaviors (for example how cached variables are handled will
certainly confuse you at first).
next prev parent reply other threads:[~2024-09-25 15:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 22:57 ./configure fails to link test program due to missing dependencies Henrik Holst
2024-09-15 16:37 ` Junio C Hamano
2024-09-15 16:47 ` brian m. carlson
2024-09-16 7:50 ` Patrick Steinhardt
2024-09-18 10:04 ` Phillip Wood
2024-09-18 22:39 ` Junio C Hamano
2024-09-24 12:10 ` Patrick Steinhardt
2024-09-24 13:59 ` Eli Schwartz
2024-09-24 14:25 ` Paul Smith
2024-09-25 4:36 ` Patrick Steinhardt
2024-09-25 6:02 ` Eli Schwartz
2024-09-25 6:04 ` Patrick Steinhardt
2024-09-26 13:55 ` Phillip Wood
2024-09-26 14:02 ` Patrick Steinhardt
2024-09-27 10:10 ` Phillip Wood
2024-09-26 16:04 ` Eli Schwartz
2024-09-27 10:00 ` phillip.wood123
2024-09-26 16:22 ` Junio C Hamano
2024-09-29 17:56 ` Johannes Schindelin
2024-09-29 18:10 ` Eli Schwartz
2024-09-30 8:50 ` Phillip Wood
2024-09-30 13:57 ` Eli Schwartz
2024-09-30 16:31 ` Junio C Hamano
2024-09-30 16:05 ` Johannes Schindelin
2024-09-25 19:15 ` Patrick Steinhardt
2024-09-25 19:17 ` Patrick Steinhardt
2024-09-24 17:39 ` Junio C Hamano
2024-09-25 15:33 ` Paul Smith [this message]
2024-09-26 1:35 ` Eli Schwartz
2024-09-26 19:42 ` Paul Smith
2024-09-24 14:31 ` Eli Schwartz
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=5bd2f41c92a00f7799bc543e229b16fa7a473760.camel@mad-scientist.net \
--to=paul@mad-scientist.net \
--cc=git@vger.kernel.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 NNTP newsgroup(s).