Search results

From Yocto Project
Jump to navigationJump to search

Page title matches

  • The current BitBake User Manual, as of Dec. 31, 2012 is quite out dated. This page serves a a The chapter layout of the BitBake User Manual is currently:
    3 KB (492 words) - 15:24, 15 January 2013
  • ...hob GUI, which aims to be a general-purpose graphical tool for interactive BitBake sessions. There are currently three GUI's in BitBake, the most recent of which is in the "extremely prototype" phase of developm
    1 KB (176 words) - 16:00, 6 September 2011
  • #REDIRECT [[BitBake/GUI/WorkInProgress]]
    40 bytes (4 words) - 00:15, 2 July 2011
  • Here are some ideas for future GUI developments for BitBake: ...ditor - build on the oetypes stuff to enable a UI which can edit arbitrary BitBake configuration variables.
    627 bytes (107 words) - 22:15, 27 May 2011
  • See planned and unplanned tasks for the hob at the [[BitBake/GUI/WorkInProgress|WIP]] page.
    696 bytes (115 words) - 19:12, 6 September 2011
  • #REDIRECT [[BitBake/GUI/Hob]]
    29 bytes (4 words) - 23:45, 1 July 2011
  • {{$||bitbake}}|Should build ''pseudo-native''.}}
    124 bytes (13 words) - 08:23, 27 May 2013
  • #REDIRECT [[BitBake Internals WIP Docs]]
    40 bytes (5 words) - 14:19, 31 October 2014
  • ...did into how toaster asks bitbake to do stuff, and how it hears about what bitbake is doing. It's not definitive and not guaranteed to be correct, but it migh == toaster asking bitbake to do stuff ==
    17 KB (2,735 words) - 15:47, 30 March 2016
  • 1,003 bytes (155 words) - 16:01, 6 September 2011
  • 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
  • 1 KB (228 words) - 14:19, 31 October 2014
  • 59 bytes (5 words) - 13:18, 27 May 2013

Page text matches

  • Here are some ideas for future GUI developments for BitBake: ...ditor - build on the oetypes stuff to enable a UI which can edit arbitrary BitBake configuration variables.
    627 bytes (107 words) - 22:15, 27 May 2011
  • bitbake package-index "bitbake <recipe> -C compile; bitbake package-index"
    655 bytes (106 words) - 10:38, 22 February 2020
  • ...hob GUI, which aims to be a general-purpose graphical tool for interactive BitBake sessions. There are currently three GUI's in BitBake, the most recent of which is in the "extremely prototype" phase of developm
    1 KB (176 words) - 16:00, 6 September 2011
  • ...required by Toaster may not be installed on the systems that currently run Bitbake without issues. ...ded; this file, named "toaster-requirements.txt", in the root directory of bitbake, lists dependencies in a pip install-compatible format.
    952 bytes (136 words) - 16:38, 17 November 2014
  • =How to debug bitbake itself with pudb= I recently had the need to debug bitbake and toaster to figure out why toaster was no longer able to save event info
    2 KB (295 words) - 23:14, 3 February 2017
  • Ever wondered what bitbake does when parsing? If you've ever wondered where bitbake spends its time during parsing, its now quite easy to find out!
    2 KB (289 words) - 13:03, 27 June 2016
  • The current BitBake User Manual, as of Dec. 31, 2012 is quite out dated. This page serves a a The chapter layout of the BitBake User Manual is currently:
    3 KB (492 words) - 15:24, 15 January 2013
  • - pip3 install -r ./bitbake/toaster-requirements.txt - pip3 install -r ./bitbake/lib/toaster/tests/toaster-tests-requirements.txt
    2 KB (264 words) - 15:08, 6 July 2016
  • ...et the SRCREV we want to test in the pseudo recipe. We then build it with "bitbake -b virtual:native:pseudo_1.8 -c populate_sysroot". Here, we're telling it t ...f pseudo-native and all the dependencies of e2fsprogs. We can however run "bitbake -b e2fsprogs -c package_qa" which does do what we want.
    2 KB (326 words) - 13:00, 5 July 2016
  • == Kernel Building w/o Bitbake == *** <code>$ bitbake core-image-minimal && bitbake core-image-minimal -c populate_sdk </code>
    3 KB (467 words) - 21:39, 15 March 2017
  • ...setting breakpoints. I wanted to be able to do this in bitbake proper aka bitbake/lib/bb/cooker.py for instance, as well as in the metadata e.g. poky/meta/cl === Debug Core Bitbake or a Bitbake Tool ===
    6 KB (925 words) - 20:29, 26 July 2017
  • *You need to run bitbake like <code> bitbake -R conf/toaster.conf -r conf/toaster-bblayers.conf <target></code>
    2 KB (437 words) - 02:56, 23 May 2018
  • git clone https://git.openembedded.org/bitbake Description=Bitbake Hash Server
    2 KB (246 words) - 17:40, 18 May 2023
  • ...<code>buildslist</code> and <code>builddelete</code>) added to <code>/poky/bitbake/lib/toaster/manage.py</code> $ python ../bitbake/lib/toaster/manage.py buildslist
    2 KB (260 words) - 15:46, 16 May 2014
  • * [[BitBake/GUI|BitBake GUI's]]
    779 bytes (86 words) - 22:57, 12 April 2023
  • : '''BitBake''': A tool that reads metadata and runs tasks. : '''OpenEmbedded-Core''': The common base set of metadata that BitBake uses. This metadata is shared between OpenEmbedded and the Yocto Project.
    1 KB (188 words) - 15:59, 20 December 2023
  • [[Toaster]] is a web-based interface to OpenEmbedded and BitBake. ...gure builds or just as a receiver for builds done on the command line with bitbake. You can launch it like this:
    3 KB (445 words) - 21:51, 30 November 2023
  • {{$||bitbake}}|Should build ''pseudo-native''.}}
    124 bytes (13 words) - 08:23, 27 May 2013
  • ...ached tasks to be used we can generate the needed signatures and configure bitbake to use those specific caches, regardless of any differences found. From the bitbake help docs:
    4 KB (660 words) - 01:51, 12 April 2017
  • $ bitbake core-image-minimal $ bitbake core-image-minimal
    4 KB (647 words) - 14:31, 13 November 2014
  • bitbake: Utilize HEAD of master |bitbake||HEAD||No||No||1.16 for danny, 1.18 for dylan, master for yocto-1.5
    989 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 localhostbeco
    5 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 world
    2 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 res
    5 KB (846 words) - 13:15, 15 October 2013
  • POKY/bitbake/bin/toaster
    357 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-diffsigs
    2 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 the
    2 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 bin
    4 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 wait
    5 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 out
    3 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.py
    6 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_configure
    3 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 the
    5 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 i
    6 KB (1,025 words) - 00:57, 14 March 2018
  • $ bitbake -c menuconfig virtual/kernel $ bitbake -c compile -f virtual/kernel
    4 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.py
    4 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-layers
    8 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 cont
    3 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 |Bitbake
    7 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 would
    8 KB (1,229 words) - 03:49, 20 August 2019
  • Bitbake tracks the release versions of every recipe and if the version increases it
    650 bytes (108 words) - 12:46, 22 November 2011
  • * A '''build system''' - based primarily on the Bitbake project and including other associated projects such as Pseudo
    812 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}}, {{#va
    18 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}}, {{#va
    17 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}}, {{#va
    17 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}}, {{#va
    17 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}}, {{#va
    18 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}}, {{#va
    18 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}}, {{#va
    18 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 ar
    6 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-kiosk
    4 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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 in
    9 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    19 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}}, {{#va
    20 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    20 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}}, {{#va
    21 KB (2,423 words) - 09:48, 23 May 2013
  • $ bitbake rpm busybox run-postinsts $ bitbake package-index
    9 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}}, {{#va
    20 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}}, {{#va
    21 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}}, {{#va
    20 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}}, {{#va
    21 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}}, {{#va
    21 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_check
    7 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}}, {{#va
    20 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}}, {{#va
    21 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}}, {{#va
    21 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}}, {{#va
    21 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}}, {{#va
    21 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}}, {{#va
    21 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}}, {{#va
    19 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}}, {{#va
    21 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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-oe
    6 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 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}}, {{#va
    19 KB (2,521 words) - 08:04, 8 April 2015
  • ...did into how toaster asks bitbake to do stuff, and how it hears about what bitbake is doing. It's not definitive and not guaranteed to be correct, but it migh == toaster asking bitbake to do stuff ==
    17 KB (2,735 words) - 15:47, 30 March 2016
  • ! [[Bitbake]] || [[Intel]]
    1 KB (103 words) - 07:18, 15 July 2013
  • <code>$ bitbake build-appliance-image</code> ...core-image-sato --runall=fetch</code> before performing the actual <code>$ bitbake core-image-sato</code> build. Also each build will be run from <code>poky</
    5 KB (753 words) - 11:54, 14 April 2023
  • {{#vardefine:bitbake| 4846 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    21 KB (2,645 words) - 11:02, 2 November 2015
  • See planned and unplanned tasks for the hob at the [[BitBake/GUI/WorkInProgress|WIP]] page.
    696 bytes (115 words) - 19:12, 6 September 2011
  • = Yocto Bug Triage BitBake Searches = |product=bitbake
    18 KB (1,981 words) - 15:22, 18 June 2015
  • ...being re-run when one would expect the existing sstate objects to be used. BitBake provides several tools for debugging these scenarios to learn what's differ $ MACHINE=qemux86-64 bitbake -S none nativesdk-glibc-initial
    9 KB (1,315 words) - 12:10, 15 February 2017
  • {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,166 words) - 11:42, 14 June 2016
  • ''bitbake-prserv --start'' ...gurations of the machine on which the service daemon is running, and then "bitbake" whatever they want to. (Please also make sure the ''BB_SIGNATURE_HANDLER''
    5 KB (759 words) - 01:35, 12 January 2012
  • * bitbake-layers: stop it displaying the warning message about not being run from the * bitbake-layers: extend it to show overlayed recipes [Paul]
    7 KB (1,115 words) - 15:46, 30 June 2011
  • {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,158 words) - 16:35, 3 March 2016
  • {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,167 words) - 15:42, 16 December 2016
  • {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,158 words) - 13:05, 17 February 2016
  • ...ct, which uses the BitBake build tool, to construct complete Linux images. BitBake and OE are combined to form a reference build host known as Poky which incl ...mark this page for reference. Implementation of bitake is covered in the [[Bitbake Internals Primer]]
    7 KB (945 words) - 21:02, 26 January 2024
  • {{#vardefine:bitbake| 6094 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,180 words) - 15:24, 29 July 2016
  • {{#vardefine:bitbake| 4126, 4127 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,128 words) - 14:15, 17 July 2015
  • *: python3, bitbake, building software, build systems ...d, particularly for parallel parsing?. Additionally it is worth noting the bitbake -P profiling option already exists and may assist.
    5 KB (731 words) - 23:42, 2 June 2021
  • {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,164 words) - 21:08, 30 May 2016
  • {{#vardefine:bitbake| 6217 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,216 words) - 21:40, 5 August 2016
  • {{#vardefine:bitbake| 5730 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,169 words) - 14:31, 15 April 2016
  • {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,159 words) - 15:27, 22 March 2016
  • $ bitbake core-image-minimal $ bitbake core-image-minimal
    7 KB (1,090 words) - 17:21, 17 October 2016
  • {{#vardefine:bitbake| 5462 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,185 words) - 17:08, 24 February 2016
  • {{#vardefine:bitbake| 5814 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,165 words) - 14:33, 27 April 2016
  • {{#vardefine:bitbake| 6522}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    18 KB (2,269 words) - 14:17, 17 November 2016
  • {{#vardefine:bitbake| 6045 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:eSDK}}, {{#var:nuc}}, {{#v
    17 KB (2,203 words) - 20:48, 29 June 2016
  • [bitbake] local_repo_dir = @os.getenv("LOCAL_REPO_DIR") + "/bitbake"
    9 KB (1,367 words) - 09:25, 20 November 2014
  • {{#vardefine:bitbake| 6253}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:eSDK}}, {{#var:nuc}}, {{#v
    18 KB (2,240 words) - 12:56, 29 August 2016
  • ...good complex example. In order to use this guide, you should set up your bitbake environment and your target as outlined in [https://wiki.yoctoproject.org/w bitbake cyrus-sasl
    7 KB (1,068 words) - 18:24, 20 September 2017
  • {{#vardefine:bitbake| 5022}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,175 words) - 11:46, 17 December 2015
  • {{#vardefine:bitbake| 4920 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,167 words) - 07:13, 30 October 2015
  • {{#vardefine:bitbake| 5639 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,200 words) - 15:40, 14 April 2016
  • {{#vardefine:bitbake| 5306 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    17 KB (2,191 words) - 14:31, 5 February 2016
  • {{#vardefine:bitbake| 6182}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:eSDK}}, {{#var:nuc}}, {{#v
    17 KB (2,199 words) - 15:24, 29 July 2016
  • {{#vardefine:bitbake| 6296}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:eSDK}}, {{#var:nuc}}, {{#v
    18 KB (2,246 words) - 19:31, 20 October 2016
  • {{#vardefine:bitbake| 6356}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:eSDK}}, {{#var:nuc}}, {{#v
    18 KB (2,296 words) - 19:03, 25 October 2016
  • ...should be self-contained and doable without a lot of context dealing with bitbake based build systems. Re-writing the recipe parser in C is probably not a go * Rewrite bbvars.py to use bitbake to find variables
    5 KB (695 words) - 13:11, 19 September 2013
  • {{#vardefine:bitbake| 6687}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:kernel}}, {{#var:eSDK}}, {
    19 KB (2,443 words) - 21:15, 21 March 2017
  • {{#vardefine:bitbake| 2905 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    22 KB (2,733 words) - 13:04, 25 September 2014
  • {{#vardefine:bitbake| 2918 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    22 KB (2,734 words) - 16:01, 29 September 2014
  • {{#vardefine:bitbake| 6805}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:eSDK}}, {{#var:nuc}}, {{#v
    18 KB (2,338 words) - 16:41, 20 February 2017
  • {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:eSDK}}, {{#var:nuc}}, {{#v
    18 KB (2,351 words) - 16:13, 28 October 2016
  • {{#vardefine:bitbake| 7352}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:eSDK}}, {{#var:nuc}}, {{#v
    18 KB (2,276 words) - 20:27, 5 June 2017
  • {{#vardefine:bitbake| 5845 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    21 KB (2,766 words) - 14:24, 20 May 2016
  • {{#vardefine:bitbake| 3778, 3779 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    21 KB (2,816 words) - 06:39, 12 May 2015
  • | Bitbake
    1 KB (163 words) - 13:02, 9 January 2015
  • {{#vardefine:bitbake| 7059}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:kernel}}, {{#var:eSDK}}, {
    19 KB (2,433 words) - 16:52, 4 May 2017
  • {{#vardefine:bitbake| 4417, 4418 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    21 KB (2,756 words) - 12:15, 16 October 2015
  • {{#vardefine:bitbake| 7118}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:kernel}}, {{#var:eSDK}}, {
    19 KB (2,437 words) - 14:37, 8 May 2017
  • {{#vardefine:bitbake| 6923 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:kernel}}, {{#var:eSDK}}, {
    19 KB (2,440 words) - 14:10, 27 April 2017
  • {{#vardefine:bitbake| 2678 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,885 words) - 14:23, 25 July 2014
  • ...ugzilla.yoctoproject.org/tr_show_case.cgi?case_id=475 User Built SDK - Use BitBake to build the toolchain] * Bitbake
    8 KB (1,317 words) - 11:20, 15 May 2013
  • {{#vardefine:bitbake| 3677, 3678 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    22 KB (2,821 words) - 08:12, 29 April 2015
  • {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:kernel}}, {{#var:eSDK}}, {
    19 KB (2,508 words) - 13:50, 9 February 2017
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    27 KB (3,657 words) - 15:12, 9 November 2017
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    27 KB (3,657 words) - 08:20, 7 November 2017
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    27 KB (3,653 words) - 06:10, 25 May 2018
  • {{#vardefine:bitbake| 2785 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,844 words) - 14:57, 1 September 2014
  • {{#vardefine:bitbake| 2785 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,844 words) - 14:55, 1 September 2014
  • {{#vardefine:bitbake| }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:kernel}}, {{#var:eSDK}}, {
    21 KB (2,630 words) - 21:08, 5 December 2017
  • {{#vardefine:bitbake| 6632}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:eSDK}}, {{#var:nuc}}, {{#v
    18 KB (2,355 words) - 19:55, 5 January 2017
  • {{#vardefine:bitbake| 3803, 3778, 3779 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    22 KB (2,860 words) - 09:20, 12 May 2015
  • {{#vardefine:bitbake| 4062, 4063 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    22 KB (2,825 words) - 16:37, 2 July 2015
  • {{#vardefine:bitbake| 2716 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,921 words) - 15:06, 30 July 2014
  • {{#vardefine:bitbake| 6846}} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:kernel}}, {{#var:eSDK}}, {
    19 KB (2,453 words) - 21:33, 23 March 2017
  • {{#vardefine:bitbake| 2569, 2571 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,873 words) - 20:55, 11 July 2014
  • ...you to bitbake the system first. If so, then type in the terminal <code>$ bitbake meta-ide-support</code> (This process would take a while). Then type again
    3 KB (511 words) - 21:44, 29 September 2017
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    29 KB (3,885 words) - 09:35, 23 May 2013
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    29 KB (3,885 words) - 08:08, 16 July 2013
  • {{#vardefine:bitbake| 2508, 2509 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,875 words) - 09:18, 4 July 2014
  • {{#vardefine:bitbake| 2508, 2509 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,875 words) - 09:12, 4 July 2014
  • {{#vardefine:bitbake| 2624, 2625 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,921 words) - 08:41, 21 July 2014
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    30 KB (4,012 words) - 13:15, 17 December 2013
  • {{#vardefine:bitbake| 3578, 3579 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    22 KB (2,758 words) - 18:48, 21 May 2015
  • {{#vardefine:bitbake| 2854, 2855 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,935 words) - 12:15, 19 September 2014
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    32 KB (4,258 words) - 11:41, 24 May 2016
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    32 KB (4,255 words) - 13:25, 16 May 2016
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    32 KB (4,255 words) - 22:22, 13 January 2016
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    32 KB (4,255 words) - 07:17, 12 January 2015
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    32 KB (4,255 words) - 10:36, 17 June 2014
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    32 KB (4,255 words) - 06:05, 17 September 2015
  • ===Bitbake===
    6 KB (859 words) - 15:33, 1 April 2013
  • ===Bitbake===
    6 KB (790 words) - 10:35, 19 March 2013
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    32 KB (4,336 words) - 08:46, 25 May 2018
  • {{#vardefine:bitbake| . }} {{#if: {{#var:bitbake}}{{#var:oe-core}}{{#var:meta-yocto}} |
    28 KB (3,789 words) - 04:10, 14 November 2018
  • {{#vardefine:bitbake| 2991, 2992 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    25 KB (3,092 words) - 16:35, 19 October 2014
  • {{#vardefine:bitbake| 3098, 3103 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    25 KB (2,944 words) - 07:46, 3 November 2014
  • | BitBake|||| | ||Poky:Build System:bitbake:(107) ||Build System & Metadata:BitBake:general
    7 KB (895 words) - 15:55, 15 May 2012
  • {{#vardefine:bitbake| 2808, 2809 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,958 words) - 15:00, 11 September 2014
  • {{#vardefine:bitbake| 2730 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (2,975 words) - 06:47, 11 September 2014
  • ...table/model definitions can be found in the [http://cgit.openembedded.org/bitbake/tree/lib/toaster/orm/models.py orm/models.py] file. ...nual/bitbake-user-manual.html#Concepts concepts] that make up openembedded/Bitbake.
    8 KB (1,400 words) - 17:52, 10 February 2016
  • {{#vardefine:bitbake| 3255, 3277 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    25 KB (3,082 words) - 16:55, 15 December 2014
  • {{#vardefine:bitbake| 3231, 3232 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    25 KB (2,996 words) - 14:03, 4 December 2014
  • === BitBake === Functional testing of BitBake, as a build engine, with all its features and components, against various c
    10 KB (1,274 words) - 13:03, 2 July 2013
  • {{#vardefine:bitbake| 3360, 3361 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    26 KB (3,230 words) - 09:55, 13 January 2015
  • ===Bitbake=== bitbake core-image-sato: 1:16.00
    12 KB (1,590 words) - 11:31, 11 April 2013
  • {{#vardefine:bitbake| 3194, 3195 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    25 KB (3,034 words) - 20:37, 20 November 2014
  • {{#vardefine:bitbake| 3046, 3047 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    25 KB (3,149 words) - 09:00, 24 October 2014
  • {{#vardefine:bitbake| 3391, 3392 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    24 KB (3,111 words) - 16:04, 26 January 2015
  • {{#vardefine:bitbake| 2948, 2949 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    26 KB (3,275 words) - 11:01, 9 October 2014
  • == Sphinx proof of concept for Bitbake Documentation == .../?h=sphinx here], and produces the following [http://docs.yoctoproject.org/bitbake/ HTML documentation].
    12 KB (1,853 words) - 15:03, 16 September 2020
  • 1.4_M4 bitbake core-image-sato: 1:16:45 1.4_M5: bitbake core-image-sato: 1:15:46
    13 KB (1,643 words) - 09:45, 9 April 2013
  • |product=BitBake,OE-Core,eSDK,Kernel,BSPs,Toaster
    995 bytes (113 words) - 21:17, 14 October 2016
  • {{#vardefine:bitbake| 4240 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    23 KB (2,779 words) - 15:35, 12 August 2015
  • |Migrated BitBake and python functions in the OE metadata to Python 3 |Bitbake improvement single config allows multiple builds for multiple machines on o
    7 KB (907 words) - 22:02, 20 April 2017
  • | BitBake||ADT Manual||minnowboard-uefi-firmware | OE-Core||BitBake User Manual||
    4 KB (606 words) - 19:06, 8 August 2016
  • $ bitbake -p ...or the same purpose, but to extract from a local repository, rather than a bitbake fetched repository
    4 KB (684 words) - 00:43, 23 August 2012
  • :: <pre>$ bitbake core-image-minimal</pre> :: <pre>$ bitbake virtual/kernel -e | grep LINUX_VERSION</pre>
    30 KB (4,189 words) - 03:33, 31 October 2018
  • #* eSDK also puts a selection of yocto tools into path - wic, devtool but not bitbake: <br /> #* 'normal mode' puts bitbake/bin/ and oe-core/scripts in PATH. Cross-toolchain can be added by the same
    8 KB (1,109 words) - 17:40, 3 November 2023
  • ...to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other '''Yocto Project''' layers. || Y or N || bgcolor="" | (Delete if ...to sending to the open source community any patches to OpenEmbedded-Core, BitBake and other '''Yocto Project''' layers. || Y || bgcolor="" |
    14 KB (1,950 words) - 18:41, 19 June 2012
  • === BitBake === Functional testing of BitBake, as a build engine with all its features and components against various con
    12 KB (1,615 words) - 15:20, 10 December 2013
  • ===Bitbake===
    8 KB (1,071 words) - 09:41, 21 February 2013
  • * bitbake * bitbake-layers
    4 KB (556 words) - 21:35, 6 November 2017
  • * Bitbake # Bitbake change should be in the bitbake-contrib repo
    12 KB (1,897 words) - 15:29, 21 March 2024
  • Tinfoil is an API that allows you to write simple utilities that call into bitbake code to read variables, parse recipes, etc
    3 KB (446 words) - 19:44, 12 January 2017
  • Each bitbake recipe should have at least the following two fields. LICENSE and LIC_
    2 KB (281 words) - 18:34, 17 April 2012
  • {{#vardefine:bitbake| 3523, 3524 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    27 KB (3,430 words) - 07:51, 12 March 2015
  • === BitBake === Functional testing of BitBake, as a build engine with all its features and components against various con
    13 KB (1,704 words) - 15:10, 29 April 2014
  • === BitBake === Functional testing of BitBake, as a build engine with all its features and components against various con
    13 KB (1,706 words) - 13:55, 9 January 2015
  • ...itory at [http://git.openembedded.org/bitbake/|http://git.openembedded.org/bitbake/]. All contributions must be upstreamed to the Bitbake repository in order to make it to the "master" branch of the poky/ reposito
    20 KB (3,143 words) - 03:45, 21 February 2017
  • {{#vardefine:bitbake| 3466, 3467 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    27 KB (3,467 words) - 16:51, 9 February 2015
  • {{#vardefine:bitbake| 3628, 3629 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    27 KB (3,508 words) - 16:36, 2 April 2015
  • {{#vardefine:bitbake| 3578, 3579 }} |run_id=0, {{#var:bitbake}}, {{#var:oe-core}}, {{#var:meta-yocto}}, {{#var:hob}}, {{#var:nuc}}, {{#va
    29 KB (3,493 words) - 13:43, 23 March 2015
  • <del>Build an qemu image, in which "bitbake core-image-minimal" work</del> bitbake, wegt... Dexuan/Edwin
    4 KB (706 words) - 08:34, 29 May 2012
  • | bgcolor="93DB70" rowspan="2" style="text-align: center;" | OE-CORE / BitBake * Verify if BBPOSTCONF and BBPRECONF work in bitbake?
    9 KB (1,345 words) - 05:22, 31 July 2018
  • <code>$ bitbake core-image-sato -c populate_sdk </code>
    3 KB (421 words) - 11:57, 20 February 2017
  • will cause your build to abort when Bitbake tries to run <code>git ls-remote</code> to resolve the tag name and is unab '''A:''' bitbake core-image-sato or core-image-sato-sdk
    13 KB (2,129 words) - 18:34, 27 December 2023
  • ===Bitbake===
    11 KB (1,364 words) - 09:17, 13 March 2013
  • ...ng accessed over the network. It acts as essentially a front-end layer for BitBake in a single-user context.
    2 KB (342 words) - 09:20, 9 July 2013
  • ===Bitbake===
    11 KB (1,370 words) - 15:06, 7 March 2013
View (previous 250 | ) (20 | 50 | 100 | 250 | 500)