'yocto-bsp list <arch> --properties' returns some kind of json listing the properties of an arch. Since some of these properties vary depending on others, conditional 'ifs' were added to the json making some kind pseudo-markup output. This output is messy and weird and should be avoided. There should be a better way of showing this, specially considering that the json generated by yocto-bsp list <arch> --properties puts all its json body inside a string, which is odd and is not useful to anybody. IFs shown on 'yocto-bsp list <arch> --properties': "if kernel_choice == "linux-yocto_4.1":" : { "smp" : { "prio" : 30 "filename" : /home/humberto/poky-dev/scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/linux-yocto_4.1.bbappend "default" : y "type" : boolean "msg" : Do you need SMP support? (y/n) } "new_kbranch" : { "prio" : 20 "filename" : /home/humberto/poky-dev/scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/linux-yocto_4.1.bbappend "type" : choicelist "branches_base" : standard "default" : standard/base "gen" : bsp.kernel.all_branches "msg" : Please choose a machine branch to base this BSP on: } "need_new_kbranch" : { "prio" : 20 "filename" : /home/humberto/poky-dev/scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/linux-yocto_4.1.bbappend "default" : y "type" : boolean "msg" : Do you need a new machine branch for this BSP (the alternative is to re-use an existing branch)? [y/n] } "existing_kbranch" : { "prio" : 20 "filename" : /home/humberto/poky-dev/scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/linux-yocto_4.1.bbappend "type" : choicelist "branches_base" : standard "default" : standard/base "gen" : bsp.kernel.all_branches "msg" : Please choose a machine branch to base this BSP on: } } IFs obtained from 'yocto-bsp list <arch> --properties -o <filename>: "if kernel_choice == \"linux-yocto_4.4\":": { "need_new_kbranch": { "prio": "20", "filename": "/home/humberto/poky-dev/scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/linux-yocto_4.4.bbappend", "default": "y", "msg": "Do you need a new machine branch for this BSP (the alternative is to re-use an existing branch)? [y/n]", "type": "boolean" }, "new_kbranch": { "default": "standard/base", "type": "choicelist", "prio": "20", "gen": "bsp.kernel.all_branches", "filename": "/home/humberto/poky-dev/scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/linux-yocto_4.4.bbappend", "msg": "Please choose a machine branch to base this BSP on:", "branches_base": "standard" }, "existing_kbranch": { "default": "standard/base", "type": "choicelist", "prio": "20", "gen": "bsp.kernel.all_branches", "filename": "/home/humberto/poky-dev/scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/linux-yocto_4.4.bbappend", "msg": "Please choose a machine branch to base this BSP on:", "branches_base": "standard" }, "smp": { "prio": "30", "filename": "/home/humberto/poky-dev/scripts/lib/bsp/substrate/target/arch/x86_64/recipes-kernel/linux/linux-yocto_4.4.bbappend", "default": "y", "msg": "Do you need SMP support? (y/n)", "type": "boolean" } }
Moving to 2.5 M1. I will work on these bugs on 2.5.
The yocto-bsp script, along with yocto-layer and yocto-kernel, will be removed from public repositories soon as they are no longer maintained. The request was sent to the mailing list [1], meaning this issue is obsolete. [1] https://lists.yoctoproject.org/pipermail/poky/2017-October/011135.html