12173 2017-10-03 22:10:26 +0000 wic cp,rm,ls of a partition e.g. ic ls myimage.wic:1/ fails if host mtools are not installed 2017-11-06 00:19:19 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools 2.4 x86 Multiple RESOLVED FIXED Medium+ normal 2.5 M1 12176 1 brian.avery sgw eduard.bartosh richard.purdie ross.burton sgw --- --- No (bug/feature does not impact docs) oldest_to_newest 77321 0 brian.avery 2017-10-03 22:10:26 +0000 Wic does depend on mtools-native and mtools-native does get built. $ wic ls myimage.wic lists partitions even if mtools is not installed on the host. This is because it is just using /bin/parted. Unfortunately, $ wic ls myimage.wic:1 fails if mtools is not installed as a host package. Turns out that we are using /usr/bin/mdir. If mtools is not installed on the host we get error: ERROR: BB Cannot run command: None, lost dependency? We should fix wic to use the mtools-native for these commands. 77627 1 sgw 2017-10-17 04:21:06 +0000 There was some missing commands in the command matching code, but also it turns out that you MUST set the native_sysroot for all the new commands, it does not currently use the same bitbake -e parsing as does the wic_create command does. I think that the parsing should be done for all commands, but it will slow things down unless bitbake-server setup is fully used. 77652 2 sgw 2017-10-17 22:53:44 +0000 wic needs a simpler method of determining it's NATIVE_SYSROOT for the simpler commands (ls, cp, rm, ...) when operating on an image to change the kernel for example. I am open to suggestions on this one. 77654 3 eduard.bartosh 2017-10-18 08:44:08 +0000 The ideas was to either allow wic to use host tools or use native sysroot specified by user. So, used doesn't have to specify native sysroot. One of the way to improve this is to make wic to use wic-tools native sys root as a default for wic (cp, ls, rm) commands. 77658 4 brian.avery 2017-10-18 16:14:35 +0000 i like the native sysroot approach, but bitbake -e is pretty slow to run for each command. any ideas on a quicker way to get the native sysroot location quickly &/or a way to find it once and reuse it? 77686 5 eduard.bartosh 2017-10-19 08:49:45 +0000 why would we want to run bitbake -e for every command? When implementing this I thought that most of the users would use host tools. For those who want to use native tools I implemented -n option to specify native sysroot. If wic is going to be run from other scripts those scripts should make sure the tools are built and provide native sysroot path to wic. There are couple of things that we discussed on irc: Richard suggested to use bitbake -e -b <recipe>, which is much faster than bitbake -e. bitbake server is going to speed up this a lot. We can just wait for it a bit. 77708 6 sgw 2017-10-19 14:58:02 +0000 Further investigation with the combination of bitbake-server and bitbake -e -b wic-tools, that provides the native sysroot info in about 1s, so that overhead is low enough I think. Regarding using the host tools, it's been mentioned before that the host tools may not behave the same as our native tools, therefore it's safer and more consistent to use the native tools to ensure consistency even if it means a slightly longer startup time. 77877 7 sgw 2017-10-30 20:19:07 +0000 Patches posted 77969 8 sgw 2017-11-06 00:19:19 +0000 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d0bb833ec7cdfb457c3cabfffaf5ae2896aa148a