News for hackers. Stuff that matters.
Re:Autodafe: Tools for freeing your project from the clammy ... by kryptiskt on Sunday April 07, 2024 @06:07AM (#39959720)
Autotools was always horrible, but it had a purpose back in the 90s, since then it's entirely vestigial and does nothing useful. It standardizes flags to config scripts and make targets, yes, but you can follow that standard without actually using autotools. It enables cross-compilation, yes, but the far biggest roadblock to successful cross-compilation is autotools, without that it's pretty easy.

Meanwhile, these days, actually trying to build on a new platform is harder if the software is using autotools than if it's using plain makefiles. Because for all the noise about feature checking, nobody including the projects using autotools, are actually using the defines from autotools, they check the OS or architecture.

Re:Autodafe: Tools for freeing your project from the clammy ... by bregma on Sunday April 07, 2024 @06:29AM (#39959815)
I currently make my living porting software to non-Linux and non-x86_64 cross-built systems, and I can vouch with certainty from lived experience that your assertions are entirely untrue.
Re:Autodafe: Tools for freeing your project from the clammy ... by dataflow on Sunday April 07, 2024 @06:09AM (#39959729)
> using the defines from autotools

Is there a list of them somewhere?

Re:Autodafe: Tools for freeing your project from the clammy ... by bonzini on Sunday April 07, 2024 @08:26AM (#39960287)
You can decide what to test for, for example

AC_CHECK_FUNCS([mlockall])

AC_CHECK_HEADERS([cpuid.h])

will define respectively HAVE_MLOCKALL and HAVE_CPUID_H.