Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
OverC + cubes distribution layer
Fetching latest commit…
Cannot retrieve the latest commit at this time.
|Failed to load latest commit information.|
meta-overc/meta-cube =================== The goal of these layers is to create a yocto build which can be deployed on a modern server to provide a useable environment which in turn can build yocto (and indeed the variant from this layer itself). A lot of the heavy lifting to achieve this has been done by the build-appliance image type of yocto, but that is limited to virtual deployment, and does not have all the development tools and/or man pages and things like tab completion that make a system "useable". This layer attempts to close that gap. Both meta-overc, and meta-overc/meta-cube should be added to your bblayers file. Dependencies ------------ This layer depends on: URI: git://github.com/openembedded/openembedded-core.git branch: master revision: HEAD prio: default URI: git://git.pokylinux.org/poky branch: master revision: HEAD layers: meta-yocto-bsp prio: default URI: git://github.com/openembedded/meta-openembedded.git branch: master revision: HEAD layers: meta-oe meta-networking meta-filesystems meta-python meta-perl meta-gnome meta-xfce meta-multimedia URI: git://git.yoctoproject.org/meta-virtualization branch: master revision: HEAD prio: default URI: git://github.com/OSSystems/meta-browser.git branch: master revision: HEAD prio: default URI: git://git.yoctoproject.org/meta-cloud-services branch: master revision: HEAD prio: default URI: git://git.yoctoproject.org/meta-qt4 branch: master revision: HEAD prio: default URI: git://git.yoctoproject.org/meta-security branch: master revision: HEAD prio: default Maintenance ----------- Send pull requests, patches, comments or questions to firstname.lastname@example.org Maintainers: Bruce Ashfield <email@example.com> License ------- All metadata is MIT licensed unless otherwise stated. Source code included in tree for individual recipes is under the LICENSE stated in each recipe (.bb file) unless otherwise stated.