ahcbb6 / meta-freertos Goto Github PK

Merely pulling this layer into a build forces a user to have a multi config setup. Having a muticonf example could be useful, but enforcing it at the level of the layer.conf seems unnecessary and should be left at the discretion of a user configuration. My proposal would be to remove defining BBMULTICONFIG in layer.conf and document its definition so a user can decide and add it for example in his local.conf based on specific needs.

Enable meta-freertos to run on a RISC-V board.

Commit 1dc180b enabled support for testimage but, doing this, it also added a hidden dependency (bug) on having debug-tweaks enabled.

The change mentioned above runs the post process commands:

execute_pre_post_process(d, d.getVar('ROOTFS_POSTPROCESS_COMMAND'))

One of these commands is rootfs_update_timestamp (which assumes that rootfs/${sysconfdir} is already created - usually done through the do_rootfs task). meta-freertos overwrites that task when using freertos-app.bbclass without satisfying the above assumption in the timestamp command.

When debug-tweaks is enabled, some other commands are added - one of which creates the required path (see postinst_enable_logging).

While this is interesting and we'd like to help grow this, it's kind of hard to use when it's not working right- and it looks like it's all a PetaLinux thing...

No documentation here is a bit of a pain and it's not obvious if it's a bug in the sense of misusing the layer or if PetaLinux is actually breaking things.