Brak opisu

Peter Kjellerstedt 51aa00f0f8 oe-init-build-env*: Update/correct comment about specifying arguments 9 lat temu
bitbake 3c66619d50 bitbake: fetch2/npm: fix ud.registry so that alternative registries can be handled 9 lat temu
documentation 01554725f5 ref-manual: Updated "Application Development SDK" section. 9 lat temu
meta 3173979532 bluez5: allow D-Bus to spawn obexd in systems without systemd 9 lat temu
meta-poky 8debfea81e local.conf.sample: Disable prelink by default 9 lat temu
meta-selftest adad26455d xcursor-transparent-theme: use a version glob in the selftest bbappend 9 lat temu
meta-skeleton 59668f2a03 linux-yocto-custom: fix typo in Upstream-Status tag 9 lat temu
meta-yocto 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 lat temu
meta-yocto-bsp bd3a1d5bdd linux-yocto: Update SRCREV for genericx86* for 4.4 9 lat temu
scripts ee4f61b7e1 oe-selftest: Fixed --list-tests-by tag option 9 lat temu
.gitignore 37cfd8080a gitignore: fix overzealous exclusion 9 lat temu
.templateconf 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 lat temu
LICENSE ef91193c51 Fix license notices for OE-Core 11 lat temu
README 9d5483c375 meta-yocto: Rename to meta-poky to better match its purpose 9 lat temu
README.hardware 790b2293d2 README.hardware: drop mention of binary-only drivers 9 lat temu
oe-init-build-env 51aa00f0f8 oe-init-build-env*: Update/correct comment about specifying arguments 9 lat temu
oe-init-build-env-memres 51aa00f0f8 oe-init-build-env*: Update/correct comment about specifying arguments 9 lat temu

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.