Usually, the standard Poky workflow includes creating package recipes and images, and deciding what will be installed on the final product image. However, a huge amount of time is spent developing, writing, testing, or adapting source code for our application.
When we write and test our application, we only care about the application itself, providing the libraries that the application requires before application development, although this can be an iterative process. However, we want a test environment that looks as similar as possible to the final one, mainly because of toolchain compatibility but also to avoid behavioral changes when we integrate the application into our product.
To help with this task, we can create a toolchain to be used externally with the Poky environment. Poky generates an SDK package that can be installed on any computer, regardless of whether Poky is installed on it. In addition, the installed toolchain is compatible with the internal one...
