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
Belen Barros Pena 7cb05bf6be bitbake: toastergui: changes to the all projects table
The 'Last build' column in the all projects table
was supposed to provide the completion time stamp
of the latest project build. Instead, it is showing
the time stamp of the latest project activity, which
includes:

* when the project was created and
* when the last build started

but not when you make a change to the configuration.

The result is that the column and the sorting are very
misleading. The template is set so that the time stamp
only shows when the project has builds (if 0 builds, no
time stamp is shown). But of course the sorting still
happens according to the value, even if it doesn't
display. The result is that, when you sort by the
'Last build' column, projects with no builds
appear listed between projects with builds, and you
have no idea why.

This patch:

* changes the column label
* its position in the table
* makes sure the time stamp always displays
* and adds help text

to reflect what the data actually means.

It also makes some small changes to other table
headings.

(Bitbake rev: 994b19ef7f633b8d463efa7022f2e17cd483a387)

Signed-off-by: Belen Barros Pena <belen.barros.pena@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-03-25 12:39:52 +00:00
bitbake bitbake: toastergui: changes to the all projects table 2015-03-25 12:39:52 +00:00
documentation dev-manual: Applied review edits to section on hostname changing 2015-03-21 00:00:48 +00:00
meta python-pygobject: Disable parallel make install in native case 2015-03-25 12:39:49 +00:00
meta-selftest oe-selftest: add a test for devtool deploy-target 2015-03-20 11:27:48 +00:00
meta-skeleton skeleton: clarify linux-yocto-custom workflow 2015-03-25 12:39:48 +00:00
meta-yocto meta-yocto/distro: Updated SANITY_TESTED_DISTROS. 2015-03-23 10:40:54 +00:00
meta-yocto-bsp meta-yocto-bsps: remove 3.10 bbappend 2015-02-21 22:05:37 +00:00
scripts yocto-bsp: Update templates to 3.19 kernel 2015-03-24 10:06:03 +00:00
.gitignore gitignore: exclude meta-selftest, drop meta-hob 2015-03-20 11:27:47 +00: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: update beaglebone entry to match KERNEL_IMAGETYPE 2014-12-21 12:38:07 +00:00
oe-init-build-env oe-init-build-env: Improve script sourcing detection. 2014-03-11 08:11:41 -07: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.