Created attachment 4690 [details] multiconfig patch I have created a very simple multiconfig cat build/conf/multiconfig/arm.conf MACHINE = "qemuarm" And then I want to modify bash: $ devtool modify mc:arm:bash #this fails NOTE: Starting bitbake server... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#1)... NOTE: Reconnecting to bitbake server... NOTE: Previous bitbake instance shutting down?, waiting to retry... NOTE: Retrying server connection (#2)... Loading cache: 100% |####################################################################| Time: 0:00:00 Loaded 2643 entries from dependency cache. Parsing recipes: 100% |##################################################################| Time: 0:00:00 Parsing of 773 .bb files complete (772 cached, 1 parsed). 2644 targets, 163 skipped, 0 masked, 0 errors. ERROR: Unable to find any recipe file matching "mc:arm:bash" $devtool modify multiconfig:arm:bash this works as expected If then I try to run: devtool build multiconfig:arm:bash NOTE: Starting bitbake server... ERROR: No recipe named 'multiconfig:arm:bash' in your workspace So I run: devtool build bash But that builds for x86 instead of for arm... The attached patch helps a bit, but it is just a horrible hack that should not be merged ;)
I'm afraid full support of multiconfig in devtool would require rewriting major part of devtool. Multiconfig allows you to run multiple machines with $ bitbake mc:qemux86:bash mc:qemuarm:bash or $ bitbake mc:*:bash while devtool allows to run only one target at a time.
Based on the comment by Tomasz, I've changed this issue to an enhancement for some time in the future. I'm not convinced that we'd ever work on it but who knows what the future holds!
Bulk move from 4.99 or 0.00 to 5.99
I have submitted a five-patch series addressing multiconfig support in devtool: https://lists.openembedded.org/g/openembedded-core/message/248498 The submitted implementation still keys workspace entries by bare PN, so the same recipe cannot be modified independently in multiple configurations simultaneously. Review has raised the need to agree on a common workspace design covering multiconfig, native, nativesdk and multilib variants. The discussion includes using one bbappend per recipe file, with settings scoped per variant and compatible variants sharing a source tree. The series is under review; the workspace design discussion remains ongoing.