Search results
From Yocto Project
Jump to navigationJump to search
- bitbake: Utilize HEAD of master |bitbake||HEAD||No||No||1.16 for danny, 1.18 for dylan, master for yocto-1.5989 bytes (133 words) - 21:48, 17 May 2013
- ...[http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/bitbake/lib/toaster/ bitbake/lib/toaster]. ...ilds.py command and launching the build process, which includes commanding bitbake and doing any Git cloning / fetching layers if needed via the localhostbeco5 KB (748 words) - 19:45, 16 August 2016
- # <code>bitbake core-image-minimal</code> # <code>bitbake -c devshell core-image-minimal</code>1 KB (172 words) - 08:08, 24 July 2013
- This data can offer insight of the time spent by the builder (<tt>bitbake</tt>) when $ bitbake world2 KB (265 words) - 21:12, 28 February 2017
- ...e EVT is the Event Translation Layer, which receive a set of events from a Bitbake build run, and builds a in-memory record set describing the build. ...s of a build run, and updates its internal state to match the state of the Bitbake server. It will generate a set of records describing the statistics and res5 KB (846 words) - 13:15, 15 October 2013
- POKY/bitbake/bin/toaster357 bytes (48 words) - 11:43, 3 November 2014
- BitBake is a build tool - a little like make, except that execution is mostly consi .../bitbake-user-manual.html#hello-world-example "hello world" example in the BitBake manual] which may be useful to see how simple this can be.7 KB (1,231 words) - 00:04, 6 April 2017
- * bitbake picking up file changes while memory resident (esp. adding files to empty d * bitbake-diffsigs2 KB (183 words) - 03:56, 21 November 2017
- $ git bisect run sh -c "cd build ; bitbake foo" ...we need to cd into build (as git bisect needs to run at the top level) and bitbake foo. If the build is successful then the script exits with success and the2 KB (416 words) - 15:40, 14 July 2016
- = What to do when bitbake says " Sad Locale, Need UTF-8" = If bitbake says:1 KB (186 words) - 22:35, 5 January 2017
- ...d image, and another for executing testimage. This is required as only one bitbake instance is allowed to be running per repository at a time. Also, additional bitbake commands are required to construct the QEMU native image and its helper bin4 KB (640 words) - 16:03, 8 March 2017
- ...configured? (i.e. it doesn't rely on staged items that don't build when I bitbake MyProject).231 bytes (40 words) - 12:33, 22 November 2011
- ...tions of the current tinfoil implementation (including it not working with bitbake's memory-resident mode) we are currently in the process of a major rewrite * If you shutdown() before the current command finishes, you get stuck in a bitbake.lock wait5 KB (819 words) - 08:56, 9 January 2017
- ...n issue we recently had). It also directly links to the correct version of Bitbake docs for the links. E.g. if a variable disappears in n+1, we need to remove === Yocto versions selection menu on Bitbake docs ===4 KB (605 words) - 16:41, 27 May 2022
- * It's awkward - you have to use <code>bitbake -c compile -f</code> or <code>bitbake -C compile</code> to force recompilation, since the build system doesn't kn * You can easily lose your changes if you're not careful e.g. running <code>bitbake -c clean</code> will wipe the directory out3 KB (576 words) - 16:47, 5 March 2024
- $ pip install -r ./poky/bitbake/toaster-requirements.txt '''3.''' Configure toaster edit /var/www/toaster/poky/bitbake/lib/toaster/toastermain/settings.py6 KB (825 words) - 00:42, 18 February 2024
- == BitBake Recipe == ...nteraction with the various ''init'' runlevels is controlled be means of a BitBake recipe. A template is shown below:4 KB (551 words) - 00:17, 19 November 2011
- ...nges that caused a rebuild since the last built version, you can use <code>bitbake-diffsigs</code> with the <code>-t</code> option: $ bitbake-diffsigs -t quilt-native do_configure3 KB (409 words) - 11:23, 8 November 2013
- *[[Image tests|Bitbake Runtime tests]] format ...bout 5 lines of code there, the test can be simply explained as: execute a bitbake build from a file that doesn't exist and verify that it shows an error. It'3 KB (504 words) - 19:55, 15 June 2016
- ...his Contains Toaster wide settings, such as the default values for certain bitbake variables. "custom.xml" in bitbake/lib/toaster/orm/fixtures/ directory. If present it will be loaded into the5 KB (671 words) - 13:46, 23 November 2016
- ...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
- {{#vardefine:bitbake| 1081, 1083... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va18 KB (2,133 words) - 13:22, 13 September 2013
- * bitbake now requires python 3.4+ ...are many Python 3 porting guides out there, or the conversion commits for Bitbake and OE-Core can be used as a guide for changes. Particular areas of note ar6 KB (874 words) - 13:54, 7 November 2016
- * Now that everything is set you can build the new image with bitbake bitbake core-image-web-kiosk4 KB (666 words) - 14:19, 31 January 2013
- {{#vardefine:bitbake| 1542 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,268 words) - 09:58, 26 November 2013
- {{#vardefine:bitbake| 1551 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,280 words) - 09:30, 3 December 2013
- {{#vardefine:bitbake| 1252, 1253 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,191 words) - 18:10, 18 September 2013
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,268 words) - 09:19, 3 December 2013
- == Using bitbake -P == ...aspects of bitbake. When the -P option is added to any usual commandline, bitbake will save out a profile.log file which contains the raw python profiling in9 KB (1,421 words) - 09:34, 6 December 2012
- {{#vardefine:bitbake| 2083 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,359 words) - 11:52, 27 March 2014
- {{#vardefine:bitbake| 2010 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,360 words) - 11:19, 13 March 2014
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,348 words) - 12:38, 24 January 2014
- saying that if you need to build the ADT tarball you can use'bitbake adt-installer'.894 bytes (129 words) - 05:36, 11 April 2011
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,354 words) - 13:34, 19 May 2014
- {{#vardefine:bitbake| 1343, 1344 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,289 words) - 12:12, 1 October 2013
- {{#vardefine:bitbake| 2333, 2334 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,371 words) - 12:19, 9 May 2014
- {{#vardefine:bitbake| 1433, 1434 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,286 words) - 10:04, 26 November 2013
- {{#vardefine:bitbake| 1273, 1274 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,288 words) - 11:29, 25 September 2013
- {{#vardefine:bitbake| 1898, 1899 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,361 words) - 09:18, 21 February 2014
- {{#vardefine:bitbake| 2000, 2001 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,358 words) - 14:55, 26 February 2014
- {{#vardefine:bitbake| 1872, 1873 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,363 words) - 13:32, 20 February 2014
- {{#vardefine:bitbake| 1582, 1583 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,352 words) - 15:47, 13 December 2013
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,367 words) - 15:47, 30 June 2014
- {{#vardefine:bitbake| 1743, 1750 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,373 words) - 09:24, 20 December 2013
- {{#vardefine:bitbake| 2129, 2130 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,364 words) - 06:37, 2 April 2014
- {{#vardefine:bitbake| 2059, 2061 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,362 words) - 07:58, 18 March 2014
- {{#vardefine:bitbake| 513... |run_id={{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,423 words) - 09:48, 23 May 2013
- $ bitbake rpm busybox run-postinsts $ bitbake package-index9 KB (1,552 words) - 15:57, 10 October 2017
- {{#vardefine:bitbake| 2419, 2420 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,366 words) - 13:00, 19 June 2014
- {{#vardefine:bitbake| 551... |run_id={{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,409 words) - 13:47, 28 May 2013
- {{#vardefine:bitbake| 2245, 2246 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,374 words) - 15:52, 22 April 2014
- {{#vardefine:bitbake| 879... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,426 words) - 07:55, 6 August 2013
- {{#vardefine:bitbake| 776... |run_id={{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,408 words) - 13:43, 25 June 2013
- ...in other Linux distros, etc). We keep the metadata via [[#BitBake_Overides|BitBake Overrides]]. The following defines the meaning of each field: bitbake world -f -c distro_check7 KB (1,079 words) - 12:37, 16 April 2015
- {{#vardefine:bitbake| 2185, 2186 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va20 KB (2,378 words) - 12:54, 9 April 2014
- {{#vardefine:bitbake| 908... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,423 words) - 07:57, 6 August 2013
- {{#vardefine:bitbake| 705... |run_id={{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,422 words) - 09:00, 13 June 2013
- * <code>bitbake</code> ...vior mentioned above. For example, let's coverage just the directory <code>bitbake/bin</code>:7 KB (1,042 words) - 22:13, 7 April 2016
- {{#vardefine:bitbake| 834, 835... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,423 words) - 12:21, 9 July 2013
- {{#vardefine:bitbake| 816... |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,412 words) - 13:17, 2 July 2013
- {{#vardefine:bitbake| 581... |run_id={{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,408 words) - 09:10, 5 June 2013
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,501 words) - 11:02, 18 January 2016
- {{#vardefine:bitbake| 756... |run_id={{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va21 KB (2,436 words) - 08:11, 16 July 2013
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,498 words) - 21:30, 9 July 2015
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,501 words) - 09:11, 30 September 2015
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,498 words) - 14:46, 2 October 2015
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,503 words) - 12:03, 10 December 2015
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,503 words) - 09:42, 21 December 2015
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,500 words) - 20:23, 2 November 2015
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,497 words) - 05:44, 22 October 2015
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,499 words) - 08:12, 24 May 2016
- {{#vardefine:bitbake| 3803 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,501 words) - 08:32, 12 May 2015
- Zephyr BOARDS typically map to bitbake MACHINES, but underscores become dashes. e.g. BOARD=arduino_101_sss maps to bitbake-layers add-layer ../meta-openembedded/meta-oe6 KB (771 words) - 10:51, 25 September 2022
- {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,500 words) - 09:12, 20 April 2016
- {{#vardefine:bitbake| 3933, 3934 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,492 words) - 16:17, 26 May 2015
- {{#vardefine:bitbake| 4296, 4297 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,499 words) - 08:56, 16 September 2015
- {{#vardefine:bitbake| 4185, 4186 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,494 words) - 14:34, 3 August 2015
- {{#vardefine:bitbake| 4240 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,501 words) - 15:19, 24 August 2015
- {{#vardefine:bitbake| 3933, 3934 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,492 words) - 11:52, 27 May 2015
- {{#vardefine:bitbake| 4062, 4063 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,493 words) - 16:44, 8 July 2015
- {{#vardefine:bitbake| 3628, 3629 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va19 KB (2,521 words) - 08:04, 8 April 2015