Changes

In recent years, the [Yocto build system|https://www.yoctoproject.org/Yocto build system] has gained popularity in the embedded world. Many silicon vendors such as NXP e Xilinx base their Board Support Packages (BSP) on this tool. Despite the fact that Yocto is very flexible and rich, it may be fairly tricky to use during the development stage, however.In particular, the unavailability of an archive of prebuilt common packages—as opposed to most of server/desktop Linux distributions—can be really annoying. As described [[Working_with_the_Yocto_build_system|here]], Yocto is basically devised to build an entire distribution from scratch indeed. To mitigate this drawback, the technique described in [[https://wiki.dave.eu/index.php/XELK-AN-003:_Package_Management_with_Yocto|this article]] can be used. In essence, one can build all the packages supported by Yocto (<code>bitbake -k world</code>) and make them available through a <code>smart</code> channel on a local server. Interestingly, in its recent BSP's, NXP indicates a little different approach, which is also open to interfacing to the Debian world. The following excerpt is taken from ==TBD==