| Brad Bishop | d7bf8c1 | 2018-02-25 22:55:05 -0500 | [diff] [blame] | 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 = "nodistro") and contains only emulated machine support. |
| 26 | |
| 27 | For information about OpenEmbedded, see the OpenEmbedded website: |
| 28 | http://www.openembedded.org/ |
| 29 | |
| Brad Bishop | 1932369 | 2019-04-05 15:28:33 -0400 | [diff] [blame^] | 30 | |
| 31 | Contribution Guidelines |
| 32 | ======================= |
| 33 | |
| 34 | A guide to submitting patches to OpenEmbedded is available at: |
| 35 | |
| 36 | http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded |
| 37 | |
| 38 | There is good documentation on how to write/format patches at: |
| 39 | |
| 40 | https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines |
| 41 | |
| 42 | |
| Brad Bishop | d7bf8c1 | 2018-02-25 22:55:05 -0500 | [diff] [blame] | 43 | Where to Send Patches |
| 44 | ===================== |
| 45 | |
| 46 | As Poky is an integration repository (built using a tool called combo-layer), |
| 47 | patches against the various components should be sent to their respective |
| 48 | upstreams: |
| 49 | |
| 50 | bitbake: |
| 51 | Git repository: http://git.openembedded.org/bitbake/ |
| 52 | Mailing list: bitbake-devel@lists.openembedded.org |
| 53 | |
| 54 | documentation: |
| 55 | Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/ |
| 56 | Mailing list: yocto@yoctoproject.org |
| 57 | |
| 58 | meta-poky, meta-yocto-bsp: |
| 59 | Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp) |
| 60 | Mailing list: poky@yoctoproject.org |
| 61 | |
| 62 | Everything else should be sent to the OpenEmbedded Core mailing list. If in |
| 63 | doubt, check the oe-core git repository for the content you intend to modify. |
| 64 | Before sending, be sure the patches apply cleanly to the current oe-core git |
| 65 | repository. |
| 66 | |
| 67 | Git repository: http://git.openembedded.org/openembedded-core/ |
| 68 | Mailing list: openembedded-core@lists.openembedded.org |
| 69 | |
| 70 | Note: The scripts directory should be treated with extra care as it is a mix of |
| 71 | oe-core and poky-specific files from meta-poky. |