@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. -
@CopperheadSec It would make even more sense to factor the apps out of the OS then use something like yocto or br to put it all together.
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.