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
Roy.Li edd8d59771 site/common-linux: move ac_cv_o_nonblock_inherited to site/common-linux
When compiling apr for no-powerpc arch, the flag ac_cv_o_nonblock_inherited
is always set to yes in cross compiling environment. This flag is intended to
think the socket, returned from accept(), inherit file status flags such as
O_NONBLOCK from the listening socket, but socket never inherits file status
from the listening socket on Linux (more information to man accept).

This is Linux-wide behaviour, so move it from meta/site/powerpc32-linux
to site/common-linux.

If ac_cv_o_nonblock_inherited is set to yes on Linux, clients can not access the
same ip address(URL) with Apache web server via http(port 80) and https(port443)
without redirection

(From OE-Core rev: f31a7ed3463e169dc93f36cc0bbe084d3f99772a)

Signed-off-by: Roy.Li <rongqing.li@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-03 14:47:55 +00:00
bitbake bitbake: build/siggen.py: Avoid removing too many stamps when cleaning 2012-11-28 14:14:07 +00:00
documentation documentation: poky-ref--manual - Updated PACKAGECONFIG 2012-12-03 13:53:01 +00:00
meta site/common-linux: move ac_cv_o_nonblock_inherited to site/common-linux 2012-12-03 14:47:55 +00:00
meta-hob meta-hob: Add a new meta-hob layer 2012-02-24 00:39:10 +00:00
meta-skeleton linux-yocto-custom: Clarify defconfig usage 2012-10-03 10:03:08 +01:00
meta-yocto maintainers: Tweak ownership of recipes 2012-12-03 14:31:29 +00:00
meta-yocto-bsp qt4: remove qt4-x11-free bbappend 2012-11-20 15:31:58 +00:00
scripts scripts/sstate-cache-management.sh: Fix stamp handling after recent layout change 2012-11-24 15:12:27 +00:00
.gitignore gitignore: Fix for poky repository 2012-10-11 13:52:14 +01:00
LICENSE LICENSE: Clarify the license recipe source code is under 2010-06-10 10:13:18 +01:00
README README: Clarify where to send patches 2012-08-22 14:05:00 +01:00
README.hardware README.hardware: extend USB-ZIP instructions 2012-04-01 12:52:03 +01:00
oe-init-build-env Various typoes fixed, all comments or output strings. 2012-03-26 12:13:05 +01: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 = "") 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, patches against the various components
should be sent to their respective upstreams.

bitbake:
    bitbake-devel@lists.openembedded.org

meta-yocto:
    poky@yoctoproject.org

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