Closed TAAPArthur closed 2 years ago
I don't know how to do it. Preferred build method is using meson.
@rkd77
Correct me if I'm wrong, but wouldn't you just need to run ./autogen.sh
and use that to create say elinks-0.14.3.tar.xz
. Another possibility is to just generate configure
(and possibly whatever else is generated) and add it to the repo directly.
Although my ideal would be dropping all of autotools and just have a Makefile... but feel like that would be very polarizing.
My main reason not to use meson is so I can use any c99 compiler like tcc. There's also the issue with complexity/transparency of meson vs a regular Makefile.
I'll also add that the only (easy to find) documentation on how to install elinks mentions the mentions configure/make. May want to consider adding a some docs to install with meson if that's the preferred. And possibly clarify if there are options in one not present in the other
My main reason not to use meson is so I can use any c99 compiler like tcc.
https://sr.ht/~lattis/muon/ should help with this. If you try building a project with CC=/path/to/tcc muon setup builddir
it will log:
LOG_W("unable to detect compiler type, falling back on posix compiler");
Personally, I'd still like to see that PR for meson to do the same thing, go through. :)
Thanks for the link. Unfortunately, muon can't yet build this repro. And I believe there are other dependencies of this repro that don't mesh well with my setup so I'll just go back to the original.
From the original elinks
Which meant one could just
./configure && make
and not require autotools. I would like to request that future releases provide a configure script.