Go to file
Paul Eggleton a897bfdbdc devtool: sdk-update: fix traceback without update server set
If the SDK update server hasn't been set in the config (when building
the extensible SDK this would be set via SDK_UPDATE_URL) and it wasn't
specified on the command line then we were failing with a traceback
because we didn't pass the default value properly - None is interpreted
as no default, meaning raise an exception if no such option exists.

Additionally we don't need the try...except anymore either because with
a proper default value, NoSectionError is caught as well.

(From OE-Core master rev: 9763c1b83362f8445ed6dff2804dd7d282861f79)

(From OE-Core rev: b2696869c1428e8ef2a198d2432121ddc2e2034c)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-15 15:51:40 +00:00
bitbake bitbake: fetch: use orig localpath when calling orig method 2016-01-08 12:10:32 +00:00
documentation bsp-guide: Updated the license statement. 2016-01-07 12:13:55 +00:00
meta classes/populate_sdk_ext: error out of install if buildtools install fails 2016-01-15 15:51:39 +00:00
meta-selftest oeqa/selftest: verify that devtool can use plugins in other layers 2015-10-21 22:56:06 +01:00
meta-skeleton linux-yocto-custom: fix typo in Upstream-Status tag 2015-10-19 17:57:58 +01:00
meta-yocto meta-yocto/distro: Updated SANITY_TESTED_DISTROS. 2015-11-03 14:02:15 +00:00
meta-yocto-bsp linux-yocto: Update Genericx86* BSP to 4.1.15 kernel 2016-01-14 15:18:29 +00:00
scripts devtool: sdk-update: fix traceback without update server set 2016-01-15 15:51:40 +00:00
.gitignore bitbake: toaster tests: gitignore and use absolute path for log file 2015-08-01 11:27:52 +01:00
.templateconf
LICENSE
oe-init-build-env oe-init-build-env: fix for build dirs that have spaces in their path 2015-04-13 22:33:24 +01:00
oe-init-build-env-memres oe-init-build-env-memres: Fix source check 2015-03-20 10:56:03 +00:00
README README: expand the Where To Send Patches section 2015-03-04 17:07:37 +00:00
README.hardware README.hardware: drop mention of binary-only drivers 2015-08-25 10:47:19 +01:00

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-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.