Re: #yocto Preferred development workflow #yocto

Chuck Wolber

We have many recipes appended to IMAGE_INSTALL in our image recipes and it works just fine.

From your description, it sounds like you could go either way. I personally prefer to keep my image recipes as clean as possible, so I push as much as I can to individual recipes. This helps with debugging later on as your project (inevitably) gets more complex.

Also... Experience has shown that the following form is a lot more readable:

IMAGE_INSTALL  = "recipe_1"
IMAGE_INSTALL += "recipe_2"
IMAGE_INSTALL += "recipe_3"
IMAGE_INSTALL += "recipe_4"
IMAGE_INSTALL += "recipe_5"

Than this:

         recipe_1 \
         recipe_2 \
         recipe_3 \
         recipe_4 \

When your repository grows large, a recursive grep for recipe_2 will make a lot more sense if "IMAGE_INSTALL += "recipe_2"" is returned instead of "recipe_2 \". The latter form gives no clue as to how recipe_2 is being referenced.


On Mon, Jul 12, 2021 at 9:36 PM ivin.lim via <> wrote:
sorry about that, right now the config files are placed in the files directory of the recipe which builds the module. 

Sample snippets of the recipe concerning this config file, I removed the rest of lines.
SRC_URI = " \
file://config.json \

do_install_append() {
install -m 0644 ${WORKDIR}/config.json ${D}/etc/directory/

If I were to have the config files placed on a separate recipe, would that mean making multiple of these recipes depending on the number of projects? 
I did thought also of adding it in the image recipe but probably this wouldn't look well if more things get added.


"Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire

Join { to automatically receive all group messages.