I have started migrating macros from the Sorts Mill Autoconf Archive to a new archive, with improvements: https://github.com/chemoelectric/chemoelectric-autoconf-archive
Mostly the improvements are making the cache variables not have names that start with things like ‘________ac’.
**"Bạn đãrowse 20 năm rồi! 🎉 Tôi đã tạo ra app Portfolio AI đơn giản: drag-and-drop, xử lý nhanh, chỉnh hình ảnh/PDF, tạo portfolio đẹp nhịp với thiết kế! ✨ AI tự tạo mockup từ architects đến sơn{màu}! 🎨 Tags: #AI #portfolio #设计师 #AutoTools #App建设 #TechNews #DesignLovers"**
*(297 characters)*
https://www.reddit.com/r/SideProject/comments/1o8ocrq/i_finally_built_my_dream_app/
Things I've discovered making my own configure script:
1. I'll never riff on #autotools again, because this shit is hard, and it's doing the best it can
2. These scripts get long, lots of stuff to check for, even in an assumed sane environment.
3. #C compilers can compile code from piped input.
4. Static compilation on #Linux, and only specifically linux, is a pain in the ass, and you basically have to check each dependency to see if it's even possible. On Win32, and BSD, it's easy though.
Właśnie zaktualizowałem trochę starych paczek #Gentoo do EAPI 8. Niektóre nie były aktualizowane od 6 lat. I wiecie, co jest najlepsze? Że nadal działają — systemy budowania działają, kod się kompiluje, programy działają. W odróżnieniu od większości nowego oprogramowania.
So I've just bumped a bunch of old #Gentoo packages to EAPI 8. Some of them haven't been updated for 6 years. And do you know what's best? They still worked — their build systems work, they compile and they just work. Unlike most of the stuff developed these days.
#fvwm3 #autotools #meson #buildsystems
A little over six months ago, I said the following:
https://bsd.network/web/@thomasadam/113340194570527011
Since six months has passed, I've now pushed to `main` a PR which does just that -- removes autotools from #fvwm3 and replaces it with meson:
https://github.com/fvwmorg/fvwm3/pull/1191
So this has been your warning.
When I release fvwm3-1.1.3, it will be using meson only.
Any questions, please do let me know. I hope downstream packagers have made the transition. :)
#fvwm3 #autotools #meson #muon #buildsystem Hey all! Please note that although fvwm3-1.1.1 is close to being relesaed, there's still a few more things left to do. Before that point, I'd like to take the opportunity to mention that as of fvwm3-1.1.1 fvwm3 is officially using meson/muon as the buildsystem of choice. Autotools has been a tremendous help over the years. Heck, fvwm as a project started long before autotools existed. But as technology changes, newer buildsystem alternatives have come along making better use of hardware, compilation speeds, etc. Indeed, because of fvwm's age -- there's a tonne of custom m4 macros -- some of which are to work around issues long since gone. With autotools recently deprecating many of these, maintaining this was becoming difficult. Hence the change. A six-month window exists once fvwm3-1.1.1 is released for downstream packagers to make the move from autotools to meson. The `main` branch in the fvwm3 repository contains both buildsystems. Please give meson some testing! A huge thanks goes to Kanjie (Matt Jolly) -- without whom none of this work would have been possible. Thanks, Matt! For more specific details. please see: https://github.com/fvwmorg/fvwm3/discussions/1068 Questions? I'm here...
I have a long-standing project which I am converting to use C++ modules. I've decided that using #perl to generate the Makefile is vastly easier than using #autotools and #cmake.
At least I can understand WTF is going on.
In the end, programmatical beats automagical.
i gotta say tho, as someone who spent the first ~15 years of my career doing web dev, going through the autotools docs was like exploring a museum. like a relic of the past
this c shit crazy