On Sat, 2018-08-18 at 18:40 +0200, Paulo Neves wrote:
> Ping.
>
> Does anybody have any comments? Also I noticed that my commit once
> was in the master-next but it was removed. Without it being in master
> I cannot submit my changes to poky mailing list with the fixes for
> the remaining
Ping.
Does anybody have any comments? Also I noticed that my commit once was
in the master-next but it was removed. Without it being in master I
cannot submit my changes to poky mailing list with the fixes for the
remaining targets.
Paulo Neves
On Sun, Aug 12, 2018 at 9:49 PM Paulo Neves wrote:
On Sun, 2018-08-12 at 21:49 +0200, Paulo Neves wrote:
> I found a bug in my code where changing a variable, for example in
> layer.conf does not re-trigger the generation of the json file
> containing the data store at the time of image creation. The json
> file is generated in
>
I found a bug in my code where changing a variable, for example in
layer.conf does not re-trigger the generation of the json file
containing the data store at the time of image creation. The json file
is generated in
ROOTFS_POSTPROCESS_COMMAND += "write_image_test_data ; " @
On Fri, 2018-08-10 at 21:37 +0200, Paulo Neves wrote:
> The testimage.bbclass invocation of controllers besides
> simpletarget and qemutarget was broken. Setting TEST_TARGET
> to class names did not work, only hardcoded values set in
> context.py were allowed. On the other hand the other
>
The testimage.bbclass invocation of controllers besides
simpletarget and qemutarget was broken. Setting TEST_TARGET
to class names did not work, only hardcoded values set in
context.py were allowed. On the other hand the other
TEST_TARGETs available were supposedly available through the
class
