Wind River Support Network

Description

Changes made to an image.inc file in a template, after a build, are not always picked up on subsequent builds. However, if a change is made to template.conf then changes in image.inc are detected.

The template processing was not checking the timestamp of the image.inc file, only the template.conf file.

Workaround

$ touch template.conf

This will modify the timestamp, resulting in chnages to image.inc being picked up.

 

Steps to Reproduce

This issue was discovered whilst helping a customer with a question about using anonymous python functions to modify the package list. I did the following steps to demonstrate to him how it could be done:

 

$ .git clone .../wrlinux-x
$ ./wrlinux-x/[setup.sh|http://setup.sh/] ...
$ cd layers/local
$ mkdir -p templates/default
$ vi templates/default/image.inc

Add the following lines:

python () {
    d.appendVar("IMAGE_INSTALL", " i2c-tools")
}

then... 


$ . environment-...
$ . oe-init-build-env
$ bitbake wrlinux-image-glibc-std

This built the i2c-tools package and included it in the rootfs as expected.

For the customer however, who already had a template.conf file, the change was not reflected in his build (he already had a build done previously, unlike in my steps).

When he then edited his template.conf file he found that the image.inc content was picked up.