generic-poky

OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705

Go to file

Niko Mauno 80fdfa4b36 package_manager.py: Explicit complementary fail When running bitbake -c populate_sdk <image_name>, it is expected that packages matching SDKIMAGE_INSTALL_COMPLEMENTARY name mask (unless declared in PACKAGE_EXCLUDE_COMPLEMENTARY) are installed to resulting SDK. Underlying mechanism issues a package manager install call for set of complementary packages. However the mechanism doesn't seem to inform the user all too obviously in case the package manager command behind install_complementary() method fails -- and since it is combined with attempt_only=True option, user might end up wondering why several -dev, -dbg packages are missing from resulting SDK. Improve associated install() method behaviour in affected OpkgPM and DpkgPM classes so that a problematic state of affairs becomes directly obvious for bitbake user, resulting in shell output like: WARNING: someimage-1.0-r0 do_populate_sdk: Unable to install packages. Command '...' returned 1: Collected errors: * Solver encountered 1 problem(s): * Problem 1/1: * - package somepkg-dev-1.0-r0.x86 requires somepkg = 1.0-r0, but none of the providers can be installed * * Solution 1: * - allow deinstallation of someotherpkg-1.1-r1.x86 * - do not ask to install a package providing somepkg-dev * Solution 2: * - do not ask to install a package providing somepkg-dev (From OE-Core rev: 2502bd591c37bf532d02dc6b37fc1e8b5224fb0a) (From OE-Core rev: 88bbc4b84ce97f82d08c841edf25e6fc29d408b0) Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 0d4459e7086fced5e9e0b4ad10378c9eddec56a8) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2018-04-05 16:26:19 +01:00
bitbake	bitbake: providers: Fix determinism issue	2018-03-09 06:12:09 -08:00
documentation	documentation: Updated manual revision table for 2.3.4 release date	2018-02-14 15:24:54 +00:00
meta	package_manager.py: Explicit complementary fail	2018-04-05 16:26:19 +01:00
meta-poky	local.conf.sample: Weakly set BB_DISKMON_DIRS	2018-01-06 10:07:33 +00:00
meta-selftest	wic-image-minimal: stop using core-image-minimal	2017-04-12 15:09:58 +01:00
meta-skeleton	useradd-example: exclude from world	2017-01-09 13:39:11 +00:00
meta-yocto/conf	meta-yocto: Rename to meta-poky to better match its purpose	2016-02-28 11:31:17 +00:00
meta-yocto-bsp	linux-yocto/4.1: generix86* bsp fix perf issue with gcc >=7	2017-09-21 17:19:25 +01:00
scripts	runqemu: Add workaround for APIC hang on pre 4.15 kernels on qemux86	2018-01-07 17:07:57 +00:00
.gitignore	add !meta-poky to .gitignore file	2016-03-26 08:06:58 +00:00
.templateconf	meta-yocto: Rename to meta-poky to better match its purpose	2016-02-28 11:31:17 +00:00
LICENSE	Fix license notices for OE-Core	2014-01-02 12:58:54 +00:00
README	meta-yocto: Rename to meta-poky to better match its purpose	2016-02-28 11:31:17 +00:00
README.hardware	README.hardware: update MPC8315E-RDB section	2017-01-16 18:08:20 +00:00
oe-init-build-env	oe-init-build-env*: Make them actually return failures	2016-03-20 23:12:30 +00:00
oe-init-build-env-memres	oe-init-build-env*: Make them actually return failures	2016-03-20 23:12:30 +00:00

README

Poky
====

Poky is an integration of various components to form a complete prepackaged
build system and development environment. It features support for building
customised embedded device style images. There are reference demo images
featuring a X11/Matchbox/GTK themed UI called Sato. The system supports
cross-architecture application development using QEMU emulation and a
standalone toolchain and SDK with IDE integration.

Additional information on the specifics of hardware that Poky supports
is available in README.hardware. Further hardware support can easily be added
in the form of layers which extend the systems capabilities in a modular way.

As an integration layer Poky consists of several upstream projects such as 
BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information 
e.g. for the hardware support. Poky is in turn a component of the Yocto Project.

The Yocto Project has extensive documentation about the system including a 
reference manual which can be found at:
    http://yoctoproject.org/documentation

OpenEmbedded-Core is a layer containing the core metadata for current versions
of OpenEmbedded. It is distro-less (can build a functional image with
DISTRO = "nodistro") and contains only emulated machine support.

For information about OpenEmbedded, see the OpenEmbedded website:
    http://www.openembedded.org/

Where to Send Patches
=====================

As Poky is an integration repository (built using a tool called combo-layer),
patches against the various components should be sent to their respective
upstreams:

bitbake:
    Git repository: http://git.openembedded.org/bitbake/
    Mailing list: bitbake-devel@lists.openembedded.org

documentation:
    Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
    Mailing list: yocto@yoctoproject.org

meta-poky, meta-yocto-bsp:
    Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp)
    Mailing list: poky@yoctoproject.org

Everything else should be sent to the OpenEmbedded Core mailing list.  If in
doubt, check the oe-core git repository for the content you intend to modify.
Before sending, be sure the patches apply cleanly to the current oe-core git
repository.

    Git repository: http://git.openembedded.org/openembedded-core/
    Mailing list: openembedded-core@lists.openembedded.org

Note: The scripts directory should be treated with extra care as it is a mix of
oe-core and poky-specific files.