diff options
| author | Adrian Dudau <adrian.dudau@enea.com> | 2013-12-12 13:38:32 +0100 |
|---|---|---|
| committer | Adrian Dudau <adrian.dudau@enea.com> | 2013-12-12 13:50:20 +0100 |
| commit | e2e6f6fe07049f33cb6348780fa975162752e421 (patch) | |
| tree | b1813295411235d1297a0ed642b1346b24fdfb12 /README | |
| download | poky-e2e6f6fe07049f33cb6348780fa975162752e421.tar.gz | |
initial commit of Enea Linux 3.1
Migrated from the internal git server on the dora-enea branch
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 49 |
1 files changed, 49 insertions, 0 deletions
diff --git a/README b/README new file mode 100644 index 0000000000..5084853835 --- /dev/null +++ b/README | |||
| @@ -0,0 +1,49 @@ | |||
| 1 | Poky | ||
| 2 | ==== | ||
| 3 | |||
| 4 | Poky is an integration of various components to form a complete prepackaged | ||
| 5 | build system and development environment. It features support for building | ||
| 6 | customised embedded device style images. There are reference demo images | ||
| 7 | featuring a X11/Matchbox/GTK themed UI called Sato. The system supports | ||
| 8 | cross-architecture application development using QEMU emulation and a | ||
| 9 | standalone toolchain and SDK with IDE integration. | ||
| 10 | |||
| 11 | Additional information on the specifics of hardware that Poky supports | ||
| 12 | is available in README.hardware. Further hardware support can easily be added | ||
| 13 | in the form of layers which extend the systems capabilities in a modular way. | ||
| 14 | |||
| 15 | As an integration layer Poky consists of several upstream projects such as | ||
| 16 | BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information | ||
| 17 | e.g. for the hardware support. Poky is in turn a component of the Yocto Project. | ||
| 18 | |||
| 19 | The Yocto Project has extensive documentation about the system including a | ||
| 20 | reference manual which can be found at: | ||
| 21 | http://yoctoproject.org/documentation | ||
| 22 | |||
| 23 | OpenEmbedded-Core is a layer containing the core metadata for current versions | ||
| 24 | of OpenEmbedded. It is distro-less (can build a functional image with | ||
| 25 | DISTRO = "") and contains only emulated machine support. | ||
| 26 | |||
| 27 | For information about OpenEmbedded, see the OpenEmbedded website: | ||
| 28 | http://www.openembedded.org/ | ||
| 29 | |||
| 30 | Where to Send Patches | ||
| 31 | ===================== | ||
| 32 | |||
| 33 | As Poky is an integration repository, patches against the various components | ||
| 34 | should be sent to their respective upstreams. | ||
| 35 | |||
| 36 | bitbake: | ||
| 37 | bitbake-devel@lists.openembedded.org | ||
| 38 | |||
| 39 | meta-yocto: | ||
| 40 | poky@yoctoproject.org | ||
| 41 | |||
| 42 | Most everything else should be sent to the OpenEmbedded Core mailing list. If | ||
| 43 | in doubt, check the oe-core git repository for the content you intend to modify. | ||
| 44 | Before sending, be sure the patches apply cleanly to the current oe-core git | ||
| 45 | repository. | ||
| 46 | openembedded-core@lists.openembedded.org | ||
| 47 | |||
| 48 | Note: The scripts directory should be treated with extra care as it is a mix | ||
| 49 | of oe-core and poky-specific files. | ||
