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
Xiaofeng Yan e8ca7c9046 chkconfig: remove link for update-alternatives to disambiguate
[YOCTO #936]
"update-alternatives" installed: one in /usr/sbin from chkconfig \
(symlinked to "alternatives"), and the other in /usr/bin \
from update-alternatives-cworth.
It appears for whatever reason that the one from chkconfig is run \
during postinst processing but if you run the script from the command \
line it gets the other one.
this is due to differences in the PATH environment variable.

The following is the sequence to call scripts after kernel booting
inittab
  -->rcS
     -->./S40networking(PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin)
     -->S98configure(call rpm-postinstall)
        #"/usr/sbin" is found prior to "/usr/bin", so update-alternatives from chkconfig is run in this script
  -->rc5.d
  -->profile(profile:4:PATH="/usr/local/bin:/usr/bin:/bin" profile:15: PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin)
  #"/usr/bin/" is found prior to "/usr/sbin", so update-alternatives from update-alternatives-cworth is run in this script

So I remove the symlink (update-alternatives linked to chkconfig). The one from update-alternatives-cworth is left alone.

(From OE-Core rev: f3a52a73251b26ead15abd4910dc82c1011ab852)

Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-08-11 19:22:06 +01:00
bitbake bitbake/usermanual: Update to be more in sync with bitbake codebase 2011-08-11 19:08:00 +01:00
documentation documentation/dev-manual/figures/bsp-dev-flow.png: Updated picture 2011-08-04 15:07:52 +01:00
meta chkconfig: remove link for update-alternatives to disambiguate 2011-08-11 19:22:06 +01:00
meta-demoapps SRC_URI, S: use BPN instead of PN for multilib case 2011-08-04 15:04:30 +01:00
meta-rt Remove -directdisk.bb recipes 2011-07-27 12:02:45 +01:00
meta-skeleton useradd-example: example recipe for using inherit useradd 2011-07-01 17:17:34 +01:00
meta-yocto local.conf.sample: Comment out BBMASK by default 2011-08-05 17:19:51 +01:00
scripts scripts/combo-layer: a simple way to script the combo-layer conf 2011-08-11 19:22:05 +01:00
.gitignore .gitignore: Update build ignores to have wildcard 2011-07-22 11:51:04 +01:00
LICENSE LICENSE: Clarify the license recipe source code is under 2010-06-10 10:13:18 +01:00
README README: Update to reflect what Poky is today 2011-04-21 13:03:52 +01:00
README.hardware README.hardware: update MPC8315E-RDB instructions 2011-07-20 17:30:22 -07:00
oe-init-build-env oe-init-build-env, scripts/oe-buildenv-internal: add error detecting for $BDIR 2011-08-02 14:32:10 +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/community/documentation

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