Search results
From Yocto Project
Jump to navigationJump to search
- ...scripts that come with BitBake / OpenEmbedded make heavy use of it - <code>bitbake-layers</code>, <code>devtool</code>, <code>recipetool</code> and <code>oe-p ...multiple variable values this is much more efficient than calling out to "bitbake -e" and parsing its output, which was the old way of getting this kind of i6 KB (1,025 words) - 00:57, 14 March 2018
- $ bitbake -c menuconfig virtual/kernel $ bitbake -c compile -f virtual/kernel4 KB (653 words) - 20:54, 27 June 2016
- Now you can run bitbake as you would normally.586 bytes (93 words) - 01:03, 13 December 2016
- ./bitbake/lib/toaster/manage.py test ./bitbake/lib/toaster/contrib/tts/runner.py4 KB (683 words) - 11:52, 15 March 2016
- ...DONE</span> : # index into all the machines that we support ? # we can ask bitbake for the MACHINE variable ...n">DONE</span> -> get from BBLAYERS or look at how do_show_layers works in bitbake-layers8 KB (1,314 words) - 13:19, 15 October 2013
- * If the project includes build system functionality, are BitBake and OpenEmbedded-Core included as components? (Y/N) * If present, can the directories containing BitBake and OpenEmbedded-Core be clearly identified within the system and only cont3 KB (462 words) - 17:18, 17 May 2012
- * Bitbake: the core task execution engine ...ariables and lets you view what files caused them to change as part of the bitbake rules parsing. This is a significant issue in early YP recipe debugging.3 KB (522 words) - 16:53, 14 October 2016
- |Bitbake |Bitbake7 KB (966 words) - 15:34, 17 February 2022
- which will then also mean that packages have increasing PR values. Bitbake itself will take care of starting and stopping the server. ...running and connect each builder to it. This is done with a command like "bitbake-prserv --host <ip> --port <port> --start" and then the configuration would8 KB (1,229 words) - 03:49, 20 August 2019
- Bitbake tracks the release versions of every recipe and if the version increases it650 bytes (108 words) - 12:46, 22 November 2011
- * A '''build system''' - based primarily on the Bitbake project and including other associated projects such as Pseudo812 bytes (120 words) - 15:35, 13 August 2013
- <code>bitbake linux-yocto -c menuconfig </code> <code>bitbake linux-yocto </code>5 KB (856 words) - 01:49, 1 November 2016
- ...s fixing patch on master for the issue). bitbake-prserv is not executable. bitbake-prserv-tool import failed with no PRSERV set.2 KB (297 words) - 05:54, 8 March 2012
- {{#vardefine:bitbake|... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va18 KB (2,037 words) - 05:40, 18 February 2019
- {{#vardefine:bitbake| 966, 967... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va17 KB (1,972 words) - 15:06, 6 August 2013
- {{#vardefine:bitbake| 928, 926... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va17 KB (1,972 words) - 10:26, 30 July 2013
- {{#vardefine:bitbake| 1043... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va17 KB (2,057 words) - 12:07, 21 August 2013
- saying that if you need to build the ADT tarball you can use'bitbake adt-installer'.865 bytes (131 words) - 06:18, 10 June 2011
- {{#vardefine:bitbake| 1045... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va18 KB (2,063 words) - 13:00, 27 August 2013
- {{#vardefine:bitbake| 1171, 1174 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va18 KB (2,123 words) - 13:22, 13 September 2013
