summaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/images
Commit message (Collapse)AuthorAgeFilesLines
* build-appliance-image: Update to sumo head revisionyocto-2.5sumo-19.0.0Richard Purdie2018-04-231-2/+2
| | | | | | (From OE-Core rev: 1b03cdf290c3c8b7f903aef696b0e1bfe763cbe0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-minimal-initramfs: use initramfs-framework for initializationCalifornia Sullivan2018-04-181-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | initramfs-framework is more modular and expandable. This change was proposed in commit 28fc6ba761ed4a47efa7c43e7f7dff5e2fe72b5e "core-image-minimal-initramfs: use initramfs-framework by default" but reverted due to the selftests runqemu.RunqemuTests.test_boot_machine_iso and runqemu.RunqemuTests.test_boot_deploy_hddimg failing. Since then, the kinks have been worked out, and missing functionality that had been missed (non-EFI installation module) has been added. Since the PACKAGE_INSTALL variable was getting so long with all these individual modules getting added, I also introduced a new INITRAMFS_SCRIPTS variable to the core-image-minimal-initramfs recipe. This variable makes the recipe look much cleaner, and also allows easier replacement or additions to the scripts. Fixes [YOCTO #10987]. (From OE-Core rev: 882ae0dcce2d96a7c286fc23b22b07972d3d8f93) Signed-off-by: California Sullivan <california.l.sullivan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2018-01-041-1/+1
| | | | | | (From OE-Core rev: 55d3aeb2d82c907a9ecd35848353c6fcb1f1e45a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image-live.bbclass: add MLPREFIX to core-image-minimal-initramfsRobert Yang2018-01-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | The 32bit core-image-minimal-initramfs should be built when build lib32-iso, e.g.: MACHINE = "qemux86-64" require conf/multilib.conf MULTILIBS = "multilib:lib32" DEFAULTTUNE_virtclass-multilib-lib32 = "x86" IMAGE_FSTYPES += "iso" $ bitbake lib32-core-image-minimal Exception: FileExistsError: [Errno 17] File exists: '/path/to/tmp/sysroots-components/core2-64/qemuwrapper-cross/usr/bin/crossscripts/qemuwrapper' -> '/path/to/tmp/work/qemux86_64-pokymllib32-linux/lib32-core-image-minimal/1.0-r0/lib32-recipe-sysroot/usr/bin/crossscripts/qemuwrapper' This was because: lib32-core-image-minimal -> core-image-minimal-initramfs core-image-minimal-initramfs -> qemuwrapper-cross lib32-core-image-minimal -> lib32-qemuwrapper-cross So we got the error, build lib32-core-image-minimal-initramfs can fix the problem. (From OE-Core rev: eee3ec805cf150f1c701427a2d182a537a67e8f5) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-live-boot-tiny: Create the initramfs-live-boot-tiny recipeAlejandro Hernandez2017-12-021-1/+1
| | | | | | | | | | | | | | | | | | The original initramfs-live-boot recipe RDEPENDS on udev, which is ok since the init script relies some of its functionality on udevadm and such, but on core-image-tiny-initramfs the init script simply drops to shell after a basic setup, so udev is not needed. This patch splits up an initramfs-live-boot-tiny recipe which does not use udev, but uses busybox-mdev instead, eudev installed about 600 extra Kilobytes to core-image-tiny-initramfs userspace, by avoiding to install eudev we achieve an even smaller footprint (almost 40% smaller). (From OE-Core rev: 7725bad91b89a291a7099b2d99789a86b028f329) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-tiny-initramfs: Enable running poky-tiny on qemux86-64Alejandro Hernandez2017-09-221-0/+2
| | | | | | | | | | | | | | | | | | | | | | Building poky-tiny for x86-64 seems fine, but when executing qemu it complains during boot time about not being able to execute init: [ 5.409730] Failed to execute /init (error -8) And then it drops to a login prompt (which it should't do on tiny) This is supposed to be complaining about init's format, it only happens on x86-64 architectures so perhaps is a 32/64 bit issue, but since core-image-tiny-initramfs does not actually provide a traditional init, the script is simply meant to drop to shell, we can workaround the issue by specifying the kernel to run the init script via busybox's sh, dropping to shell correctly on x86-64 leaving x86 unaffected. (From OE-Core rev: f15de8cf177f8f736c180c1dcaa942a9931865d4) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-tiny-initramfs: initramfs recipes should not generate an actual ↵Alejandro Hernandez2017-09-211-4/+3
| | | | | | | | | | | | | | image file core-image-tiny-initramfs was used to generate a wic image, which was conceptually wrong since initrafms recipes should only generate the boot artifacts that can later be used by another recipe to generate an image using the tool of their choice. (From OE-Core rev: 2a4c65636821be48a8e585491bec40b5048be25d) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: include proxy on pip3 installationLeonardo Sandoval2017-08-231-1/+5
| | | | | | | | | | | | | | | | | Otherwise, we get timeouts, leading to errors: pip._vendor.requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded with url: /pypi/pip/json (Caused by ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7ff741bb3ef0>, 'Connection to pypi.python.org timed out. (connect timeout=5)')) WARNING: TOPDIR/tmp/work/qemux86-poky-linux/build-appliance-image/15.0.0-r0/temp/run.do_populate_poky_src.185123:1 exit 1 from 'pip3 install --user -I -U -v -r TOPDIR/tmp/work/qemux86-poky-linux/build-appliance-image/15.0.0-r0/rootfs/home/builder/poky/bitbake/toaster-requirements.txt' DEBUG: Python function do_image finished Complete log at [1] [1] http://errors.yoctoproject.org/Errors/Build/43393/ (From OE-Core rev: 8291156c30e54a05ad455dda2b8540a570bb0f4a) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Don't use COREBASE/LICENSE for checksummingSaul Wold2017-08-181-2/+1
| | | | | | | | | | This file lists the licenses that the OE-Core meta data falls under but should not be used as a LIC_FILES_CHKSUM, use the MIT license file. (From OE-Core rev: e12fa3ac08962accb6585e2aa1c486e7852d174d) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image: Convert vmdk/vdi/qcow2 to strict CONVERSION_CMD typesTom Rini2017-07-301-3/+3
| | | | | | | | | | | | | | | | | The vmdk/vdi/qcow2 IMAGE_FSTYPEs predate wic. As such, they provide some similar underlying functionality in order to produce a "disk" image that in turn can be converted into different formats that various hypervisor types work with. They do not however provide the ability for other disk image types to be converted into these same output types. Furthermore, they are less flexible than what wic does provide. This drops the old style vmdk/vdi/qcow2 types and re-introduces them under the CONVERSION_CMD framework. The equivalent of vmdk is now wic.vmdk and so forth for the other types. (From OE-Core rev: 929ba563f1bc7195c4981b8e139c432b2cc388ea) Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "core-image-minimal-initramfs: use initramfs-framework by default"Richard Purdie2017-07-301-1/+1
| | | | | | | | This reverts commit 28fc6ba761ed4a47efa7c43e7f7dff5e2fe72b5e since it causes runqemu.RunqemuTests.test_boot_machine_iso and runqemu.RunqemuTests.test_boot_deploy_hddimg to fail in oe-selftest. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-minimal-initramfs: use initramfs-framework by defaultNg, Wei Tee2017-07-271-1/+1
| | | | | | | | | | | | Use the initramfs-framework for initialization by default due to the modularity and expansibility. [YOCTO #10987] (From OE-Core rev: 28fc6ba761ed4a47efa7c43e7f7dff5e2fe72b5e) Signed-off-by: Ng, Wei Tee <wei.tee.ng@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionyocto-2.3pyro-17.0.0Richard Purdie2017-05-011-1/+1
| | | | | | (From OE-Core rev: 123962018251dfb1d6ca5aa5c0d02534007de3ab) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2017-04-291-1/+1
| | | | | | (From OE-Core rev: 4fe59183dae7c556363bc885cfda11a38c0d2d47) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2017-04-291-1/+1
| | | | | | (From OE-Core rev: 766bef5755521960e24ed7192214bf66bbee8354) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2017-04-211-1/+1
| | | | | | (From OE-Core rev: e584be78f92ee6f08f570c239698d56ac78d05f9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2017-04-201-1/+1
| | | | | | (From OE-Core rev: 0126fe8934ecae3c91e441c4e1f5a86a15837679) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2017-04-201-1/+1
| | | | | | (From OE-Core rev: 0b8167fa3e792dac272e24e3f06af88ada90ff14) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: ensure pod2man present in BAJuro Bystricky2017-03-161-1/+1
| | | | | | | | | | | | | | | | | | "pod2man" went missing from BA, but it is required. This patch fixes the Toaster error: <...> ERROR: These tools appear to be unavailable in PATH, please install them in order to proceed: pod2man <...> [YOCTO#11144] (From OE-Core rev: 562c184d52db2182eafde3cf9866606145784deb) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: fix build errorsJuro Bystricky2017-03-161-0/+2
| | | | | | | | | | | | Remove any symlinks before creating new ones to avoid potential build errors such as: FileExistsError: [Errno 17] File exists: '../../usr/src/kernel' -> ... ' (From OE-Core rev: 376aa835dd70e646a00706272db6f5ac7f419ce7) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: use pip3-nativeJuro Bystricky2017-03-161-2/+4
| | | | | | | | | | | | | Do not rely on pip3 being installed on the host. Use pip3-native instead. [YOCTO#10909] [YOCTO#11022] (From OE-Core rev: 0c349f06b6b026e9bbd3e9a8188e3d8645fd00d9) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* run-postinsts: simplify the logic of whether to install it to imagesAlexander Kanavin2017-03-141-1/+1
| | | | | | | | | | The logic is scattered all over the place, but amounts to "install, unless the rootfs is read only". Let's express that directly. (From OE-Core rev: 697804229a172125ce7d3bfc9b343812d6fe3240) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revision2.3_M2Richard Purdie2017-02-011-1/+1
| | | | | | (From OE-Core rev: 303868c8976523342026817c6aa1a04ce0408c5d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-tiny-initramfs: Fix error message shown after a successful initrd ↵Alejandro Hernandez2017-01-311-0/+12
| | | | | | | | | | | | | | | boot When booting core-image-tiny-initramfs, since we want to live on initrd, on purpose, we never find a rootfs image to switch root to, this causes init to show an error as it would with other images, this patch replaces the message shown to the user, avoiding confusion when it was indeed a successful boot. (From OE-Core rev: 3378c322247f5c261f40d06480379da9a24e3082) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-tiny-initramfs: Add and image creating image artifacts onlyTom Zanussi2017-01-311-0/+30
| | | | | | | | | | | | | | | | Add an image that simply creates image artifacts using image-live-artifacts support instead of creating an actual image. The image artifacts can then be subsequently assembled by an external tool such as wic to create an actual image. This eliminates redundant image creation when using such tools. (From OE-Core rev: 97237259a9acb9a1511823914dea52b9719fbafd) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2017-01-231-1/+1
| | | | | | (From OE-Core rev: 40463f9d806b478a887128345a66135ef6fa2fe8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: support for ToasterJuro Bystricky2017-01-162-3/+93
| | | | | | | | | | | | | | | | | | | | | | | Various changes needed to enable to run Toaster in the Build Appliance: 1. Pre-install packages as specified by the file "bitbake/toaster-requirements.txt" 2. Include pip3 in the image 3. Include tzdata in the image (needed by django) 4. Bump SRCREV to a commit with proper settings.py (ALLOWED_HOSTS) for Django 1.8.16 5. Added README_VirtualBox_Toaster.txt to provide steps for configuring VirtualBox network adapters (NAT or Bridged) and steps to launch Toaster [YOCTO#10767] (From OE-Core rev: dffbac64bbf86c91247ba7373b3b5bd6af24103f) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Fix incorrect PATHJuro Bystricky2016-11-061-1/+1
| | | | | | | | | | | | | | | | | When modifying the PATH variable in .bashrc, double quote characters were used, resulting in expanding the variable $PATH with the value of PATH of the system building the Build Appliance. The original intent was to enter an un-expanded (literal) $PATH. In order to that, one must use single quotes instead of double quotes. [YOCTO#10434] [YOCTO#10504] (From OE-Core rev: 6238faf901956e2a350315a66ca1ce557deaa513) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-261-1/+1
| | | | | | (From OE-Core rev: 0e651676817a0513abf50741d0ba28b35edbae09) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: add /sbin to PATHJuro Bystricky2016-10-251-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | runqemu script fails with an error when executed in Build Appliance. Typical use case: $ bitbake core-image-minimal $ runqemu qemux86 Observed error: runqemu - ERROR - In order for this script to dynamically infer paths ...snip... runqemu-ifup, runqemu-ifdown or ip not found The error is caused by the fact that "ip" is located in /sbin, however /sbin is not in user's ("builder") PATH. To fix this we add /sbin to PATH. The simplest place to do this is in user's .bashrc. [YOCTO#10434] (From OE-Core rev: 7561514454c20a86e9e126af80dcf114ccd23535) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-191-1/+1
| | | | | | (From OE-Core rev: 327e4bf5a84d5b49ccc65927df622c9ef6302d55) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-111-1/+1
| | | | | | (From OE-Core rev: 1a2311c8fa9a3703568cd390c44639fe3335023e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-111-1/+1
| | | | | | (From OE-Core rev: 70b9b1f5bbc07d97f90b62793bf2c5aa01884436) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-10-111-1/+1
| | | | | | (From OE-Core rev: c33cd0b3d274d2c4253ff98f85b7ca4fced0aedb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Create image in correct locationJuro Bystricky2016-09-191-2/+1
| | | | | | | | | | | | | | | | Due to the recipe now using variable IMGDEPLOYDIR instead of DEPLOY_DIR_IMAGE, the final Build Appliance image ended up being created in a wrong location. This patch assures the final ZIP image is created in identical location as before: tmp/deploy/images/<machine>/Yocto_Build_Apliance.zip [YOCTO#10274] (From OE-Core rev: 5ac0604fdc7d5b783011c43d476210b427b5dae0) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image: Deploy images to IMGDEPLOYDIREd Bartosh2016-09-041-4/+4
| | | | | | | | | | | | | | | | | Changed deployment directory from DEPLOY_DIR_IMAGE to IMGDEPLOYDIR to make sstate machinery to do final deployment and generate manifest. Renamed variable deploy_dir to deploy_dir_image in selftest code to avoid confusion with DEPLOYDIR variable. Updated the code of rootfs.py:Rootfs class to use IMGDEPLOYDIR variable as it's now used as a new deployment destination. (From OE-Core rev: 6d969bacc718e21a5246d4da9bf9639dcae29b02) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revision2.2_M1Richard Purdie2016-06-211-1/+1
| | | | | | (From OE-Core rev: 9431698a88430f0fa892d9b270c0849c4d3d2486) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-06-211-1/+1
| | | | | | (From OE-Core rev: b4ccfdfeece9665d9ef8967495fdb1a1d5f494b4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Add LC_ALL setting and drop pseudo piecesRichard Purdie2016-06-161-7/+1
| | | | | | | | | | | | The pseudo pieces here date from times gone by when bitbake ran in two phases. Its long since obsolete and can be dropped. Also set LC_ALL so that bitbake works correctly and uses the local we're already installing into the image so we have utf-8 available. (From OE-Core rev: 7c1f1fc3d739d778886208d6833c34e6ca1dc148) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Install network componentsJuro Bystricky2016-06-161-1/+2
| | | | | | | | | | | | | Explicitly add network components into Build Appliance image, do not rely on packagegroup-self-hosted to pull them in. Network related dependencies were removed from packagegroup-self-hosted. YOCTO #9758 (From OE-Core rev: fc0d9c27b88a691b0fea98b9a2b2a4f3e978ec87) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to master head revisionRichard Purdie2016-06-161-1/+1
| | | | | | (From OE-Core rev: bdad088488842f64d9fa973097e9797a901f1d02) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: update version to 15.0.0Alexander Kanavin2016-06-041-0/+0
| | | | | | | (From OE-Core rev: f969c6249a18e175a2dbd80b20dfdc99a83432dc) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-{minimal, testmaster}-initramfs: set COMPATIBLE_HOSTMartin Jansa2016-05-221-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | * use the same COMPATIBLE_HOST restriction as initramfs-live-install(-testfs) to resolve ugly error when trying to build them e.g. for ARM: ERROR: Nothing RPROVIDES 'initramfs-live-install-testfs' (but /home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-extended/images/core-image-testmaster-initramfs.bb RDEPENDS on or otherwise requires it) ERROR: initramfs-live-install-testfs was skipped: incompatible with host arm-oe-linux-gnueabi (not in COMPATIBLE_HOST) NOTE: Runtime target 'initramfs-live-install-testfs' is unbuildable, removing... Missing or unbuildable dependency chain was: ['initramfs-live-install-testfs'] ERROR: Required build target 'core-image-testmaster-initramfs' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-testmaster-initramfs', 'initramfs-live-install-testfs'] ERROR: Nothing RPROVIDES 'initramfs-live-install' (but /home/jenkins/oe/world/shr-core/openembedded-core/meta/recipes-core/images/core-image-minimal-initramfs.bb RDEPENDS on or otherwise requires it) ERROR: initramfs-live-install was skipped: incompatible with host arm-oe-linux-gnueabi (not in COMPATIBLE_HOST) NOTE: Runtime target 'initramfs-live-install' is unbuildable, removing... Missing or unbuildable dependency chain was: ['initramfs-live-install'] ERROR: Required build target 'core-image-minimal-initramfs' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-minimal-initramfs', 'initramfs-live-install'] (From OE-Core rev: 8016b51d81ca9ed1567effa9d2870b1d98684350) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: use 'lnr' instead of 'ln -sr'Ming Liu2016-05-211-2/+2
| | | | | | | | | For portability, not all hosts are running sufficiently new coreutils. (From OE-Core rev: b06d9ad6c235584f3cb12244bc5437ca7977a0c8) Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel: moves KERNEL_SRC_PATH to bitbake.confMing Liu2016-05-191-1/+1
| | | | | | | | | | "/usr/src/kernel" is being hard-coded in multiple recipes so far, move its definition to bitbake.conf. (From OE-Core rev: eb9f900527e02ca08a1de14b4ac773f513bb1ee4) Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance: Switch to master branch post releaseRichard Purdie2016-04-291-1/+1
| | | | | | (From OE-Core rev: 04d5dff40803ef6d6c150542e812889e07e719d9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to krogoth head revisionyocto-2.1krogoth-15.0.0Richard Purdie2016-04-191-2/+2
| | | | | | (From OE-Core rev: 9838f8d077d16e52ad592879d65a9e8350b93075) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Load TUN at startupJuro Bystricky2016-04-181-2/+6
| | | | | | | | | | | | | | | | | | | | This patch addresses the issue of not being able to execute "runqemu" in the Build Appliance. The root cause of the problem was that TAP/TUN was not available, although required by "runqemu". In addition, the recommended remedy $ sudo modprobe tun would fail for two reasons: modprobe not in PATH (user builder), and "iptables" located in /usr/sbin but expected in /sbin. [YOCTO #9437] (From OE-Core rev: 65db0a29be91a157522cf02ebb21961b8ba55759) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* images: zero out the rootfs_extra_space in initramfs imagesStephano Cetola2016-04-181-0/+1
| | | | | | | | | | | Setting IMAGE_ROOTFS_EXTRA_SPACE impacts the initramfs images, results in an error about INITRAMFS_MAXSIZE. (From OE-Core rev: 3ee82430f3f3eb62cbc949658808d109222e8b24) Signed-off-by: Stephano Cetola <stephano.cetola@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Support for VirtualBox guest additionsJuro Bystricky2016-04-112-2/+87
| | | | | | | | | | | | | | | | | | Add support for VirtualBox guest additions. The additions are built inside the Build Appliance VM. For this to be possible, the environment for out-of-tree kernel module builds must be present and set up properly. A README file with detailed steps on how to build the guest additions is placed in the home directory of the user "builder" as well. The main purpose of the guest additions is to allow sharing folders between the host and Build Appliance VM. [YOCTO #8073] (From OE-Core rev: a11c9fd6e3ca9a76c866f13fcc12b8d2e60a4097) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-13 18:36:37 +0000