@RichFelker It's an improvement. But not by much; the number of CMakeFiles you have to change just to start contributing overwhelms.
-
-
-
@cr1901 No, it's not. CMake is IMake 2.0. -
@cr1901 People who don't understand make are doomed to reinvent it, EXTREMELY POORLY. -
@RichFelker Autoconf's fatal flaw was tying itself to POSIX-like tools too heavily. I shouldn't have to use bash to compile s/w on Windows. -
@cr1901 Completely disagree there. POSIX is the portability standard; Windows is broken. Thankfully midipix is fixing that. -
@RichFelker Does musl libc provide a Windows libc :P? The only other libc I'm aware of for Windows besides Microsoft's is OpenWatcom's. -
@cr1901 Actually yes. See the midipix project. http://www.midipix.org -
@RichFelker I did see the page already; I did a double take when I read about musl having Windows support :P.
End of conversation
New conversation -
-
-
@RichFelker CMake sucks but ninja support makes this a step forwards. The make build system is horrible for actually working on LLVM. -
@CopperheadSec Then replace it with a GOOD make-based build system. Not CMake. -
@RichFelker AOSP is moving away from make in master to a very sane structured layer on top of ninja: https://android.googlesource.com/platform/bionic/+/master/libc/Android.bp …. -
@RichFelker AOSP's make build system already used an extremely templated, structured approach and they're mapping it directly to this. -
@RichFelker Using build systems like make (especially autotools) and CMake based on awful domain specific programming languages isn't great. -
@RichFelker It works fine for simple projects but it's too unreadable and complex so there's a lot that can and does go wrong at scale. -
@RichFelker Compare to https://android.googlesource.com/platform/bionic/+/master/libc/Android.mk …. Pretty much the same thing, but they're dropping a lot of unnecessary flexibility/overhead. -
@RichFelker The source: https://android.googlesource.com/platform/build/blueprint/+/master …. AOSP is enormous so it makes a lot of sense for them to roll their own tool. - 1 more reply
New conversation -
-
-
@RichFelker not a fan of CMake? Either way, including two (or three, for lldb) distinct build systems is rather awkwardThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@richfelker Gross. -
@dev_console@RichFelker Lemme guess: autoconf is gpl, cmake is bsd-ish? -
@landley@richfelker Aside from that being true, I think it stems from the same attitude that prefers C++ to C for these things. -
@dev_console@RichFelker I mean LLVM is Apple's baby, and they've been doing "the great GPL purge" for years now: http://meta.ath0.com/2012/02/05/apples-great-gpl-purge/ …
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.