I am a little bit amazed that I have to write this article in my blog, but I started a new project a few months ago and I was speechless of how they worked on yocto. So here I will briefly explain why devtool exists and all the things that you could do with it.
When you started with Yocto for the first time. It could be overwhelm to not know what to expect. I remember when I started working with Yocto my first thought was: "This is very cool, but also extremely complex". I spent a good amount of time with my developer leader and myself until I grasp a good amount of knowledge about this tool. In this blog, I want to summarize five things that you need to know before working with Yocto.
While working on various embedded projects, I often ran into the same issue with handling custom-developed libraries. Each Makefile or CMakeLists.txt manages the compiler and linker flags for these libraries individually. But what happens when you have ten applications using that library and you need to make a breaking change? You have to update the build script for all ten applications. As you can imagine, in large projects, this is a nightmare. In this blog, you will see a better way to handle this using pkgconfig.
Yet Another Opinion about Yocto vs Buildroot... If you ever come across to work with YANG, I hope you understand the reference. If you don't have a clue what I am talking about, don't worry, I have no clue of YANG and SNMP until a few months ago 😅. As you may get for the title, I will just write why I think Yocto and OpenEmbedded is the right tool for building your custom Linux Embedded systems, even for personal projects. Let's go into it 🤓
Building Linux systems is still tough, but Yocto and Buildroot simplify it a lot. In this blog, you will see the problems of building a Linux embedded device from scratch and why these tools changes the game for better.