undefined | Better HN

0 pointseschneider1y ago0 comments

This is truth. I've done a lot of work bringing up custom boards with both Yocto and Buildroot and I rather like Yocto. But yeah, first project with Yocto was painful. It's rather well documented, but one really needs a good idea of what's going on to really know what you're even looking for.

That said, once you get it figured out, it's very flexible and largely logical. :)

0 comments

ahartmetz1y ago

IME, the documentation is kinda useless when the going gets tough. But the code is surprisingly easy to follow.

eschneiderOP1y ago

The docs are good in the "I think there should be a way to do X" and if you have a good sense of how Yocto is organized, you'll know where to check if X exists. That's...not a trivial thing.

ahartmetz1y ago

True. For the most part, the documentation tells you what you can do in general terms and where (which file / variable). That is useful, but not enough to know how to do it.

j / k navigate · click thread line to collapse

0 pointseschneider1y ago0 comments

That said, once you get it figured out, it's very flexible and largely logical. :)

0 comments

ahartmetz1y ago

IME, the documentation is kinda useless when the going gets tough. But the code is surprisingly easy to follow.

eschneiderOP1y ago

The docs are good in the "I think there should be a way to do X" and if you have a good sense of how Yocto is organized, you'll know where to check if X exists. That's...not a trivial thing.

ahartmetz1y ago

True. For the most part, the documentation tells you what you can do in general terms and where (which file / variable). That is useful, but not enough to know how to do it.

j / k navigate · click thread line to collapse