sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity
OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705
36,571 Commits 8 Branches 0 Tags 142 MiB
Python 37.9%
BitBake 15.7%
C 15.5%
PHP 10%
Shell 7.2%
Other 13.4%
Go to file
Elliot Smith a0791c19db bitbake: toasterui: Create per-build logs 
Rather than relying on bug 8411, which is conveniently creating
separate log files for each of our builds, create our own
log file for each build.

The log files are created in the same tmp directories that
bitbake users, but are timestamped to the millisecond to avoid
name collisions.

Each log file is opened on a ParseStarted event (for builds
triggered by Toaster) or BuildStarted event (for builds on the
command line: Toaster doesn't get the ParseStarted event
for command-line builds).

The log file is closed on the BuildCompleted event, or if the
build fails.

Because we start logging on ParseStarted for Toaster builds,
we're able to capture the "Build Configuration" section which
bitbake writes to output.

[YOCTO #8373]

(Bitbake rev: 7974203cd8bc66dff1fcc55f8723dedefaf72840)

Signed-off-by: Elliot Smith <elliot.smith@intel.com>
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
 		2015-10-29 22:05:36 +00:00
bitbake bitbake: toasterui: Create per-build logs 2015-10-29 22:05:36 +00:00
documentation toaster manual: Updated the set up and use chapter 2015-10-27 07:28:22 +00:00
meta perl: Remove errornous extra path-specs for Module::Build based modules 2015-10-29 07:31:17 +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 toasterconf: update meta-yocto to jethro and drop dizzy 2015-10-11 08:11:30 +01:00
meta-yocto-bsp linux-yocto: Update SRCREV for genericx86* BSPs 2015-10-07 00:36:47 +01:00
scripts runqemu-export-rootfs: update location of unfsd binary 2015-10-29 07:31:17 +00:00
.gitignore bitbake: toaster tests: gitignore and use absolute path for log file 2015-08-01 11:27:52 +01:00
.templateconf .templateconf: New file for customized template defaults 2014-03-11 08:14:27 -07:00
LICENSE Fix license notices for OE-Core 2014-01-02 12:58:54 +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
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 

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.