Some poky/oe-embedded recipes may require additional host tools. For example, to build Zephyr SDK in a container, the following are needed: makeself, p7zip-full, libwxgtk3.5-dev, libwxgtk3.5, libreadline-dev, wx3.5-headers (The version of wxgtk is distro dependent, Ubuntu 16 needs 3.5)
Are you using https://github.com/crops/poky-container for the Zephyr SDK builds?
yes, that is the one. While on the subject, I think adding "nano" editor would be quite useful as well for people like me that constantly need cheat sheet for vi
poky-container uses Ubuntu 14.04 as base. The upstream Ubuntu 14.04 repos have only version 3.0 of the following packages. Is this going to work for the Zephyr SDK builds? E: Unable to locate package libwxgtk3.5-dev E: Couldn't find any package by regex 'libwxgtk3.5-dev' E: Unable to locate package libwxgtk3.5 E: Couldn't find any package by regex 'libwxgtk3.5' E: Unable to locate package wx3.5-headers E: Couldn't find any package by regex 'wx3.5-headers'
(In reply to comment #3) > poky-container uses Ubuntu 14.04 as base. The upstream Ubuntu 14.04 repos > have only version 3.0 of the following packages. Is this going to work for > the Zephyr SDK builds? > > E: Unable to locate package libwxgtk3.5-dev > E: Couldn't find any package by regex 'libwxgtk3.5-dev' > E: Unable to locate package libwxgtk3.5 > E: Couldn't find any package by regex 'libwxgtk3.5' > E: Unable to locate package wx3.5-headers > E: Couldn't find any package by regex 'wx3.5-headers' I recently added all the distros that are in base as well, so really you could use any of them. https://hub.docker.com/r/crops/poky/tags/ However, the real question is although there are some amount of tools needed for "bootstrapping" oe-core usage, why can't these tools instead have native recipes in the metadata?
If native recipes for these host tools will be used as part of the Zephyr SDK build then no CROPS-specific changes are required. No modifications to poky-container are needed. Closing.