Skip to contentSkip to conversation

bitbake-setup feedback - long subpath + hardcoding machine and distro

DISCUSSION ChenQi 2 participants 3 messages Nov 12, 2025

lore
Share & tools
lore

ChenQi

author
#0 lore raw

Hi All,

I'd like to provide one feedback on bitbake-setup.

The subpath is unnecessarily long, e.g., poky-master-poky-distro_poky-machine_qemux86-64. And it's hardcoding machine and distro values.

Such design might be reasonable for testing infrastructure, but it's not good user experience for developers.

For example, what if I want to to build things for qemuarm64? I'm using layers under the a subpath with the name of poky-master-poky-distro_poky-machine_qemux86-64 but I'm building for qemuarm64. This feels a little weird.

Regards,
Qi

#1 lore raw
Quoted 11 lines · ChenQi

The subpath is unnecessarily long, e.g., poky-master-poky-distro_poky-machine_qemux86-64. And it's hardcoding machine and distro values.
Such design might be reasonable for testing infrastructure, but it's not good user experience for developers.

For example, what if I want to to build things for qemuarm64? I'm using layers under the a subpath with the name of poky-master-poky-distro_poky-machine_qemux86-64 but I'm building for qemuarm64. This feels a little weird.

The directory name is hardcoding the choices made during 'bitbake-setup init'. The reason is that if you want to run 'init' again and make different choices, it would be able to create a different directory, and not error out because the one it wants to create already exists.

There's a patch for bitbake-setup to give you a chance to write in something shorter interactively. You can also pass in a shorter choice with --setup-dir option. You can also use --skip-selection to omit the selection of distro or machine, or anything else that is asked at 'init', and then you will also get a shorter directory. But the default needs to ensure different setup directories don't clash, and so the choices are hardcoded in them. If there's something else we could do, please tell so.

Alex

author
#2 lore raw
Quoted 26 lines · Alexander Kanavin
Quoted 10 lines · ChenQi

The subpath is unnecessarily long, e.g., poky-master-poky-distro_poky-machine_qemux86-64. And it's hardcoding machine and distro values.
Such design might be reasonable for testing infrastructure, but it's not good user experience for developers.

For example, what if I want to to build things for qemuarm64? I'm using layers under the a subpath with the name of poky-master-poky-distro_poky-machine_qemux86-64 but I'm building for qemuarm64. This feels a little weird.

The directory name is hardcoding the choices made during 'bitbake-setup init'. The reason is that if you want to run 'init' again and make different choices, it would be able to create a different directory, and not error out because the one it wants to create already exists.

There's a patch for bitbake-setup to give you a chance to write in something shorter interactively. You can also pass in a shorter choice with --setup-dir option. You can also use --skip-selection to omit the selection of distro or machine, or anything else that is asked at 'init', and then you will also get a shorter directory. But the default needs to ensure different setup directories don't clash, and so the choices are hardcoded in them. If there's something else we could do, please tell so.

Quoted 1 line

Alex

Hi Alex,

Thanks a lot for your help. The '--setup-dir-name' satisfies what I need.

Regards,
Qi