💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › kisslinux-2023-06-06.txt captured on 2024-05-10 at 14:03:04.
⬅️ Previous capture (2023-06-14)
-=-=-=-=-=-=-
[2023-06-06T06:14:43Z] <sewn> 🐈🐈🐈🐈
[2023-06-06T12:27:57Z] <sad_plan> hi
[2023-06-06T15:52:08Z] <sewn> hi sad_plan
[2023-06-06T16:31:13Z] <sewn> chikcen yes
[2023-06-06T18:39:35Z] <sewn> anyone tried to replace auto{conf,make} with https://github.com/cheusov/mk-configure ?
[2023-06-06T18:39:38Z] <sewn> looks neat
[2023-06-06T18:51:18Z] <sad_plan> ive not, but ive tried some of the libtool replacement, and none of them worked for my usecase anyway. but ill check it out anyway.
[2023-06-06T18:56:28Z] <sewn> what are some libtool replacements you know?
[2023-06-06T18:57:15Z] <sewn> i can't seem to get mk-configure/bmkdep to compile
[2023-06-06T19:10:10Z] <sad_plan> slibtool, jlibtool, just to name a couple. neither worked for me atleast. either missing flags or something, i dunno. been some time since I messed with them
[2023-06-06T19:12:56Z] <sewn> bmake is weird, somehow proginstall (default install target) tries to install as root instead of user because of BINOWN/BINGRP
[2023-06-06T19:14:04Z] <sewn> something might be wrong with my system
[2023-06-06T19:27:56Z] <sewn> i dont think mk-configure replaces autoconf/automake oops
[2023-06-06T19:30:44Z] <sad_plan> > lightweightreplacement for GNU autotools
[2023-06-06T19:30:51Z] <sad_plan> says so in about, so thats their claim
[2023-06-06T19:33:34Z] <sewn> i would still need autoconf to generate configure and makefile
[2023-06-06T19:33:51Z] <sewn> it doesnt seem to replace it
[2023-06-06T19:34:06Z] <sewn> unless i'm using it incorrectly, their readme simply states to run mkcmake on a project with configure.ac and makefile.in
[2023-06-06T19:40:05Z] <sad_plan> to generate Makefile and configure from *.ac and *.in youd use autools/libtool. so it should replace it. now wether it works in a different story
[2023-06-06T19:40:53Z] <sewn> men I would rather use cmake/meson than ac and in
[2023-06-06T19:41:13Z] <sewn> hell I'd rather write a meson/make file for some small projects using autoconf or find alternatives because damn
[2023-06-06T19:53:54Z] <sad_plan> id avoid cmake initially, aswell as meson. regular makefiles, possibly with a configure script is the best imo
[2023-06-06T19:54:06Z] <sad_plan> i would choose meson over cmake though
[2023-06-06T20:02:12Z] <sewn> personally i like meson as a specification, the program itself isnt great. the dependency management, scripting of meson i believe is pretty nice
[2023-06-06T20:02:39Z] <sewn> makefile is cool too but i wouldn't imagine it would be working for stuff that needs much dependencies or rather advanced building and generation of other things
[2023-06-06T20:03:06Z] <sad_plan> thats where the configure script comes in, with bigger projects
[2023-06-06T20:04:41Z] <sewn> or cmake/meson
[2023-06-06T20:05:22Z] <sad_plan> well. yeah, but I like configure better, or meson. less so cmake
[2023-06-06T20:05:34Z] <sewn> configure is great untill you have to generate it
[2023-06-06T20:06:05Z] <sad_plan> thats the worst when thats the case
[2023-06-06T20:06:10Z] <sad_plan> in that case, id rather just use meson
[2023-06-06T20:06:17Z] <sewn> like maybe if configure didn't generate shell scripts and was a C program that just runs and generates on the project..