README.poky 2.7 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. Poky
  2. ====
  3. Poky is an integration of various components to form a complete prepackaged
  4. build system and development environment. It features support for building
  5. customised embedded device style images. There are reference demo images
  6. featuring a X11/Matchbox/GTK themed UI called Sato. The system supports
  7. cross-architecture application development using QEMU emulation and a
  8. standalone toolchain and SDK with IDE integration.
  9. Additional information on the specifics of hardware that Poky supports
  10. is available in README.hardware. Further hardware support can easily be added
  11. in the form of layers which extend the systems capabilities in a modular way.
  12. As an integration layer Poky consists of several upstream projects such as
  13. BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information
  14. e.g. for the hardware support. Poky is in turn a component of the Yocto Project.
  15. The Yocto Project has extensive documentation about the system including a
  16. reference manual which can be found at:
  17. http://yoctoproject.org/documentation
  18. OpenEmbedded-Core is a layer containing the core metadata for current versions
  19. of OpenEmbedded. It is distro-less (can build a functional image with
  20. DISTRO = "nodistro") and contains only emulated machine support.
  21. For information about OpenEmbedded, see the OpenEmbedded website:
  22. http://www.openembedded.org/
  23. Contribution Guidelines
  24. =======================
  25. A guide to submitting patches to OpenEmbedded is available at:
  26. http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
  27. There is good documentation on how to write/format patches at:
  28. https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
  29. Where to Send Patches
  30. =====================
  31. As Poky is an integration repository (built using a tool called combo-layer),
  32. patches against the various components should be sent to their respective
  33. upstreams:
  34. bitbake:
  35. Git repository: http://git.openembedded.org/bitbake/
  36. Mailing list: bitbake-devel@lists.openembedded.org
  37. documentation:
  38. Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
  39. Mailing list: yocto@yoctoproject.org
  40. meta-poky, meta-yocto-bsp:
  41. Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp)
  42. Mailing list: poky@yoctoproject.org
  43. Everything else should be sent to the OpenEmbedded Core mailing list. If in
  44. doubt, check the oe-core git repository for the content you intend to modify.
  45. Before sending, be sure the patches apply cleanly to the current oe-core git
  46. repository.
  47. Git repository: http://git.openembedded.org/openembedded-core/
  48. Mailing list: openembedded-core@lists.openembedded.org
  49. Note: The scripts directory should be treated with extra care as it is a mix of
  50. oe-core and poky-specific files from meta-poky.