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