| Age | Commit message (Collapse) | Author | Files |
|---|
|
* initrd images need to be prepared with mkimage to be usable from u-boot
Signed-off-by: Steffen Sledz <sledz@dresearch.de>
Acked-by: Martyn Welch <martyn.welch@gefanuc.com>
Acked-by: Tom Rini <tom_rini@mentor.com>
|
|
Acked-By: Michael 'Mickey' Lauer <mlauer@vanille-media.de>
Acked-by: Koen Kooi <koen@openembedded.org>
|
|
|
|
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
fr-fr and thus locale-fr packages were bing omitted)
|
|
This reverts commit 736c06e8d8efa79d3d2bc512f13a51f0f63412e2
as this change breaks future versions of bitbake.
See the OE mailing list, in the "Bitbake runqueue performance improvement"
thread for a discussion on why this isn't the best way to solve
multi-image problem and that other better solutions exist.
|
|
|
|
Set IMAGE_KEEPROOTFS to something other than the empty string to keep
tmp/rootfs around after image creation, otherwise it will be removed, as it's
not a fully functional filesystem, and causes much confusion among users as a
result.
Signed-off-by: Chris Larson <clarson@mvista.com>
Acked-by: Tom Rini <trini@embeddedalley.com>
Acked-by: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
|
|
|
|
* this method will install all linguas in $IMAGE_LINGUAS for all packages installed into the rootfs
* currently opkg only, guarded with a check
|
|
Allows parallel build for different images.
Acked-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
IMAGE_VARS usage forces images to have init, dev management, login
management and other stuff. In cases where you don't need any of those
(like initramfs images or other special-purpose images) you need to
override 4 variables in order to get clean image that only installs
things from IMAGE_INSTALL.
So, this changes IMAGE_VARS to more meaningful IMAGE_BOOT and makes it
possible to build images without boot components with single
IMAGE_BOOT="".
Acked-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Koen Kooi <koen@openembedded.org>
|
|
Places do_rootfs function before do_install in image creation process.
This change allows multiimage builds, when one image depends on another (before
that second image creation raced with do_rootfs for the first one) and uses
it for some purpose.
Multiimage builds are useful in situations like creating an installer image
with initramfs (built in OE) and an image of the target FS (also built in OE)
or for building virtualized system images to be placed on target FS.
Signed-off-by: Koen Kooi <koen@openembedded.org>
|
|
rootfs_ipk: task-boot change fixes
|
|
update users as well
Acked-By: Marcin Juszkiewicz <hrw@openembedded.org>
|
|
IMAGE_ROOTFS_SIZE
|
|
During my work for OpenedHand I wrote one usefull thing which we used for
ext2/ext3 images - autosizing.
In few words: it checks how big rootfs is, adds IMAGE_EXTRA_SPACE amount
of kilobytes to it and gives that size to genext2fs.
|
|
generation (from Poky)
|
|
|
|
|
|
once works (#4193). Remap PACKAGE_INSTALL variable so packages to install can include names which are changed by debian.bbclass. (from poky)
|
|
* death to ipkg!
|
|
|
|
* A standalone task to deploy built image to the location specified
by DEPLOY_TO variable (likely passed via environment).
Assumes ${IMAGE_FSTYPES} is a single value!
|
|
DISTRO value.
* Some distros override DISTRO var to hack overrides right, etc. Yet, original
value may be needed sometimes. For example, bbimage expects DISTRO to be what
user set/passed it, not something else.
* TODO: After interim cleanup during preparation of this patch, it turns out
that angstrom is the only distro to (ab)use DISTRO overriding. It may make sense
to instead get its OVERRIDES value right.
|
|
("bogofeed").
* If set to a base URL of ipk deploy dir as exported by HTTP/FTP, it will create
set of feed configs to use deploy subdirs as feeds.
|
|
|
|
export correctly, add BZR fetcher config (from poky)
|
|
|
|
(LICENCE default, setup of RDEPENDS and default IMAGE_BASENAME)
|
|
|
|
uses USE_DEVFS and we should consider removing it,
|
|
|
|
with modifications)
|
|
|
|
|
|
|
|
correct operation with bitbake 1.8.x. Old behaviour is maintained in a special legacy anonymous function in base.bbclass. The patch is an improved version of the one discussed on the mailing list.
|
|
image types.
|
|
want to log in at all.
|
|
on populate staging for do_rootfs (both from poky)
|
|
things like updater.sh for the zaurus get deployed with the image. This change on affects bitbake 1.7.x users who *will* need to use the latest 1.7.x version from svn.
|
|
image.bbclass to prepare for rootfs_deb/bbclass (from poky)
|
|
prepare for deb packaging
|
