Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | meta: Convert IMAGE_TYPEDEP to use override syntax | Richard Purdie | 2021-08-04 | 1 | -1/+1 |
| | | | | | | | | | The IMAGE_TYPEDEP variable would make more sense to match the form of the other image override variables, convert it to use the overrides format. (From OE-Core rev: 8573f6b2a7af9867da0b21936ffd2cd2a417de1d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> | ||||
* | image-container.bbclass: Error if not using linux-dummy | Randy Witt | 2017-02-19 | 1 | -0/+18 |
| | | | | | | | | | | | | | | | | | | | In the typical case of a container, the user doesn't particularly care about the kernel version used. Since using linux-dummy prevents building a kernel in the most common case, alert the user if they choose a container image, but don't also specify linux-dummy. In the cases the user actually does want to build against particular kernel headers, etc, they can override by setting IMAGE_CONTAINER_NO_DUMMY = "1". [YOCTO #9502] (From OE-Core rev: f0645e172bb839803d616f19307e1e81e0d204c0) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> | ||||
* | image-container.bbclass: Add the "container" IMAGE_FSTYPES | Randy Witt | 2017-02-19 | 1 | -0/+3 |
The "container" fstype does very little other than pick tar.bz2 as the actual image type and disable installation of ROOTFS_BOOTSTRAP_INSTALL. [YOCTO #9502] (From OE-Core rev: e45f074b792a43aa2fd84a5a3f0e20bf1d88ad7e) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |