1Bitbake 2======= 3 4BitBake is a generic task execution engine that allows shell and Python tasks to be run 5efficiently and in parallel while working within complex inter-task dependency constraints. 6One of BitBake's main users, OpenEmbedded, takes this core and builds embedded Linux software 7stacks using a task-oriented approach. 8 9For information about Bitbake, see the OpenEmbedded website: 10 http://www.openembedded.org/ 11 12Bitbake plain documentation can be found under the doc directory or its integrated 13html version at the Yocto Project website: 14 https://docs.yoctoproject.org 15 16Contributing 17------------ 18 19Please refer to 20http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded 21for guidelines on how to submit patches, just note that the latter documentation is intended 22for OpenEmbedded (and its core) not bitbake patches (bitbake-devel@lists.openembedded.org) 23but in general main guidelines apply. Once the commit(s) have been created, the way to send 24the patch is through git-send-email. For example, to send the last commit (HEAD) on current 25branch, type: 26 27 git send-email -M -1 --to bitbake-devel@lists.openembedded.org 28 29Mailing list: 30 31 http://lists.openembedded.org/mailman/listinfo/bitbake-devel 32 33Source code: 34 35 http://git.openembedded.org/bitbake/ 36 37Testing: 38 39Bitbake has a testsuite located in lib/bb/tests/ whichs aim to try and prevent regressions. 40You can run this with "bitbake-selftest". In particular the fetcher is well covered since 41it has so many corner cases. The datastore has many tests too. Testing with the testsuite is 42recommended before submitting patches, particularly to the fetcher and datastore. We also 43appreciate new test cases and may require them for more obscure issues. 44