21 Jun
2024
21 Jun
'24
12:41 a.m.
Someone clearly never used imake...
There's a reason that the xmkmf command ends in the two letters it does,
and I'm never going to believe it's "make file".
Adam
On Thu, Jun 20, 2024 at 11:34 AM Greg A. Woods <woods(a)robohack.ca> wrote:
At Thu, 20 Jun 2024 01:01:01 -0400, Scot Jenkins via
TUHS <tuhs(a)tuhs.org>
wrote:
Subject: [TUHS] Re: Version 256 of systemd boasts '42% less Unix
philosophy' The Register
"Greg A. Woods" <woods(a)robohack.ca> wrote:
The alternative _is_ to reimplement the build process.
For example, see:
https://github.com/robohack/yajl/
This example is a far more comprehensive rewrite than is usually
necessary as I wanted a complete and portable example that could be used
as the basis for further projects.
An example of a much simpler reimplementation:
http://cvsweb.NetBSD.org/bsdweb.cgi/src/external/mit/ctwm/bin/ctwm/Makefile…
--
Greg A. Woods <gwoods(a)acm.org>
Kelowna, BC +1 250 762-7675 RoboHack <woods(a)robohack.ca>
Planix, Inc. <woods(a)planix.com> Avoncote Farms <woods(a)avoncote.ca>
I will not ever allow cmake to run, or even
exist, on the machines I
control...
I'm not a fan of cmake either.
How do you deal with software that only builds with cmake (or meson,
scons, ... whatever the developer decided to use as the build tool)?
What alternatives exist short of reimplementing the build process in
a standard makefile by hand, which is obviously very time consuming,
error prone, and will probably break the next time you want to update
a given package?