It looks like a new iteration of Buildroot, which kind of slid behind Yocto/OE in professional community. Is there any summary why this would be preferable to either of those?
So now the question is, why didn't it get traction in over a decade?
Not excluding the possibility of an "hidden gem" here, and people in embedded tend to be conservative, but to be honest "professional" and "easy" in the same sentence looks a bit suspicious to me.
I personally very much prefer buildroot over yocto, which feels bloated (my opinion only). However buildroot has some shortcomings that are important to me (for example it lacks a package system, which makes it difficult to do partial updates). Ptxdist adds this and also some other useful stuff, such as a mechanisms for “layers” (similar to Yocto).
I guess for me it just hits the sweet spot between simplicity and flexibility.
My company has been using it professionally since 2014, and we are very happy with the results.
9 comments
[ 3.0 ms ] story [ 28.1 ms ] threadNot excluding the possibility of an "hidden gem" here, and people in embedded tend to be conservative, but to be honest "professional" and "easy" in the same sentence looks a bit suspicious to me.
- It couldn't find a feature-gap between buildroot and OE/YP in order to differentiate itself and attract new developers
- It is more or less a one-vendor project
Why no traction? Not sure about that. Perhaps it was difficult to communicate the benefits in an area where buildroot was already well established.
I guess for me it just hits the sweet spot between simplicity and flexibility.
My company has been using it professionally since 2014, and we are very happy with the results.