diff options
author | 2022-01-19 15:29:59 +0000 | |
---|---|---|
committer | 2022-01-24 19:26:35 +0800 | |
commit | d78dd539377b2947e73336f45afb5f1c4812bf9d (patch) | |
tree | 2fed10b2b2b4ea2abf92fd073dd933316fe44f38 | |
parent | e9cada633ac9a5a41c318af4e7688619523558d3 (diff) | |
download | meta-zephyr-d78dd539377b2947e73336f45afb5f1c4812bf9d.tar.gz meta-zephyr-d78dd539377b2947e73336f45afb5f1c4812bf9d.tar.bz2 meta-zephyr-d78dd539377b2947e73336f45afb5f1c4812bf9d.zip |
README.txt: Document generate-zephyr-machine use
This commit just adds some documentation on how to use the machine
generation recipe.
Signed-off-by: Eilís Ní Fhlannagáin <elizabeth.flanagan@huawei.com>
Signed-off-by: Naveen Saini <naveen.kumar.saini@intel.com>
-rw-r--r-- | README.txt | 16 |
1 files changed, 16 insertions, 0 deletions
@@ -105,6 +105,22 @@ or $ MACHINE=qemu-nios2 bitbake zephyr-kernel-test-all -c testimage +Generating OE Machines based on Zephyr board definitions +======================================================== +We currently have a recipe called generate-zephry-machines which will go through +and attempt to create an OE machine conf file for every board in Zephyr. + +This is run via: + +MACHINE=qemu-x86 bitbake generate-zephyr-machines + +The output is then put in the normal deploy dir. This recipe is really only +useful for maintainers. There is currently no way to use the Zephyr board +definition in a single step build. So if you wish to regenerate those machines, +you will need to run the above, copy the conf files from the deploy dir to the +machine conf directory and then run your build. This shouldn't need to happen +often. + Contributing ============ |