Home
last modified time | relevance | path

Searched full:bitbake (Results 1 – 25 of 540) sorted by relevance

12345678910>>...22

/OK3568_Linux_fs/yocto/poky/bitbake/doc/
H A Dreleases.rst11 - :yocto_docs:`3.4 BitBake User Manual </3.4/bitbake-user-manual/bitbake-user-manual.html>`
12 - :yocto_docs:`3.4.1 BitBake User Manual </3.4.1/bitbake-user-manual/bitbake-user-manual.html>`
13 - :yocto_docs:`3.4.2 BitBake User Manual </3.4.2/bitbake-user-manual/bitbake-user-manual.html>`
19 - :yocto_docs:`3.3 BitBake User Manual </3.3/bitbake-user-manual/bitbake-user-manual.html>`
20 - :yocto_docs:`3.3.1 BitBake User Manual </3.3.1/bitbake-user-manual/bitbake-user-manual.html>`
21 - :yocto_docs:`3.3.2 BitBake User Manual </3.3.2/bitbake-user-manual/bitbake-user-manual.html>`
22 - :yocto_docs:`3.3.3 BitBake User Manual </3.3.3/bitbake-user-manual/bitbake-user-manual.html>`
23 - :yocto_docs:`3.3.4 BitBake User Manual </3.3.4/bitbake-user-manual/bitbake-user-manual.html>`
24 - :yocto_docs:`3.3.5 BitBake User Manual </3.3.5/bitbake-user-manual/bitbake-user-manual.html>`
30 - :yocto_docs:`3.1 BitBake User Manual </3.1/bitbake-user-manual/bitbake-user-manual.html>`
[all …]
H A Dindex.rst4 BitBake User Manual
13 bitbake-user-manual/bitbake-user-manual-intro
14 bitbake-user-manual/bitbake-user-manual-execution
15 bitbake-user-manual/bitbake-user-manual-metadata
16 bitbake-user-manual/bitbake-user-manual-fetching
17 bitbake-user-manual/bitbake-user-manual-ref-variables
18 bitbake-user-manual/bitbake-user-manual-hello
31 | BitBake Community
33 | <bitbake-devel@lists.openembedded.org>
H A Dbitbake.15 .TH BITBAKE 1 "November 19, 2006"
19 BitBake \- simple tool for the execution of tasks
21 .B bitbake
26 .B bitbake
32 \fBbitbake\fP is a program that executes the specified task (default is 'build')
33 for a given set of BitBake files.
64 drop into the interactive mode also called the BitBake shell.
74 read the specified file before bitbake.conf
117 Run bitbake without UI, the frontend can connect with bitbake server itself.
120 The name/address for the bitbake server to bind to.
[all …]
/OK3568_Linux_fs/yocto/poky/bitbake/doc/bitbake-user-manual/
H A Dbitbake-user-manual-hello.rst7 BitBake Hello World
14 context of BitBake. The tutorial describes how to create a new project
15 and the applicable metadata files necessary to allow BitBake to build
18 Obtaining BitBake
21 See the :ref:`bitbake-user-manual/bitbake-user-manual-hello:obtaining bitbake` section for
22 information on how to obtain BitBake. Once you have the source code on
23 your machine, the BitBake directory appears as follows::
44 At this point, you should have BitBake cloned to a directory that
47 Setting Up the BitBake Environment
50 First, you need to be sure that you can run BitBake. Set your working
[all …]
H A Dbitbake-user-manual-execution.rst9 The primary purpose for running BitBake is to produce some kind of
13 can execute the ``bitbake`` command with options that cause it to
17 This chapter describes BitBake's execution process from start to finish
21 $ bitbake target
24 the BitBake command and its options, see ":ref:`The BitBake Command
25 <bitbake-user-manual-command>`" section.
29 Prior to executing BitBake, you should take advantage of available
51 The first thing BitBake does is parse base configuration metadata. Base
53 to determine what layers BitBake needs to recognize, all necessary
54 ``layer.conf`` files (one from each layer), and ``bitbake.conf``. The
[all …]
H A Dbitbake-user-manual-intro.rst9 Welcome to the BitBake User Manual. This manual provides information on
10 the BitBake tool. The information attempts to be as independent as
11 possible regarding systems that use BitBake, such as OpenEmbedded and
21 Fundamentally, BitBake is a generic task execution engine that allows
24 BitBake's main users, OpenEmbedded, takes this core and builds embedded
27 Conceptually, BitBake is similar to GNU Make in some regards but has
30 - BitBake executes tasks according to the provided metadata that builds up
34 files. The metadata provides BitBake with instructions on what tasks
37 - BitBake includes a fetcher library for obtaining source code from
46 - BitBake includes a client/server abstraction and can be used from a
[all …]
H A Dbitbake-user-manual-metadata.rst9 BitBake files have their own syntax. The syntax has similarities to
76 occurs, you can use BitBake to check the actual value of the suspect
82 $ bitbake -e
86 ``local.conf``, ``bblayers.conf``, ``bitbake.conf`` and so forth)
97 $ bitbake recipename -e | grep VARIABLENAME=\"
105 Outside of :ref:`functions <bitbake-user-manual/bitbake-user-manual-metadata:functions>`,
106 BitBake joins any line ending in
128 BitBake does not interpret escape sequences like "\\n" in variable
165 :ref:`bitbake-user-manual/bitbake-user-manual-metadata:immediate variable
323 BitBake-style Python functions. See the ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:she…
[all …]
H A Dbitbake-user-manual-ref-variables.rst9 This chapter lists common variables used by BitBake and gives an
17 - The variables listed in this glossary are specific to BitBake.
20 - Also, variables exist in other systems that use BitBake (e.g. The
30 Lists recipe names (:term:`PN` values) BitBake does not
31 attempt to build. Instead, BitBake assumes these recipes have already
41 :ref:`Azure Storage fetcher <bitbake-user-manual/bitbake-user-manual-fetching:fetchers>`
53 The directory in which BitBake executes functions during a recipe's
100 the path of the build. BitBake's output should not (and usually does
108 Specifies the path to a log file into which BitBake's user interface
116 Defines how BitBake handles situations where an append file
[all …]
/OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/selftest/cases/
H A Dbbtests.py9 from oeqa.utils.commands import runCmd, bitbake, get_bb_var, get_bb_vars
20 # Test bitbake can run from the <builddir>/conf directory
23 self.assertEqual(bitbake('-e').status, 0, msg = "bitbake couldn't run from \"conf\" dir")
25 # Test bitbake can run from the <builddir>'s parent directory
30 …self.assertEqual(bitbake('-e', env=my_env).status, 0, msg = "bitbake couldn't run from builddir's …
32 # Test bitbake can run from some other random system location (we use /tmp/)
37 … self.assertEqual(bitbake('-e', env=my_env).status, 0, msg = "bitbake couldn't run from /tmp/")
42 result = bitbake('m4-native')
50 bitbake('m4-native')
51 bitbake('m4-native -cclean')
[all …]
H A Dbblayers.py16 result = runCmd('bitbake-layers layerindex-show-depends meta-poky')
18 …contents, msg = "openembedded-core should have been listed at this step. bitbake-layers layerindex…
21 result = runCmd('bitbake-layers show-cross-depends')
25 result = runCmd('bitbake-layers show-layers')
31 result = runCmd('bitbake-layers show-appends')
35 result = runCmd('bitbake-layers show-overlayed')
45 result = runCmd('bitbake-layers flatten %s' % testoutdir)
50 …self.assertTrue(find_in_contents, msg = "Flattening layers did not work. bitbake-layers flatten ou…
54 result = runCmd('bitbake-layers show-layers')
55 …esult.output, "This test cannot run with meta-skeleton in bblayers.conf. bitbake-layers show-layer…
[all …]
H A Dbuildoptions.py12 from oeqa.utils.commands import bitbake, get_bb_var, get_bb_vars
21 bitbake("-c clean core-image-minimal")
24 bitbake("core-image-minimal")
30 bitbake("core-image-minimal")
36 bitbake("ccache-native")
42 self.add_command_to_tearDown('bitbake -c clean %s' % recipe)
43 bitbake("%s -c clean" % recipe)
44 bitbake("%s -f -c compile" % recipe)
55 bitbake("core-image-sato core-image-weston")
62 res = bitbake("delay -c delay", ignore_status = True)
[all …]
H A Dbblogging.py7 from oeqa.utils.commands import bitbake
17 result = bitbake("logging-test -c shelltest -f", ignore_status = True)
25 result = bitbake("logging-test -c shelltest -f", ignore_status = True)
33 result = bitbake("logging-test -c shelltest -f -v", ignore_status = True)
42 result = bitbake("logging-test -c shelltest -f -v", ignore_status = True)
51 result = bitbake("logging-test -c pythontest_exec_func_shell -f",
60 result = bitbake("logging-test -c pythontest_exec_func_shell -f",
69 result = bitbake("logging-test -c pythontest_exec_func_shell -f -v",
79 result = bitbake("logging-test -c pythontest_exec_func_shell -f -v",
89 result = bitbake("logging-test -c pythontest_exit -f", ignore_status = True)
[all …]
H A Darchiver.py7 from oeqa.utils.commands import bitbake, get_bb_vars
31 bitbake('-c clean %s %s' % (include_recipe, exclude_recipe))
32 bitbake("-c deploy_archives %s %s" % (include_recipe, exclude_recipe))
62 bitbake('-c clean %s %s' % (target_recipe, native_recipe))
63 bitbake("%s -c deploy_archives %s" % (target_recipe, native_recipe))
99 bitbake('-c clean %s %s' % (' '.join(target_recipes), ' '.join(native_recipes)))
100 bitbake('-c deploy_archives %s %s' % (' '.join(target_recipes), ' '.join(native_recipes)))
132 bitbake('-n selftest-nopackages selftest-ed')
143 bitbake('-c clean %s' % (target))
144 bitbake('-c deploy_archives %s' % (target))
[all …]
/OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/bldcontrol/
H A Dlocalhostbecontroller.py2 # BitBake Toaster Implementation
76 def setCloneStatus(self,bitbake,status,total,current,repo_name): argument
77 bitbake.req.build.repos_cloned=current
78 bitbake.req.build.repos_to_clone=total
79 bitbake.req.build.progress_item=repo_name
80 bitbake.req.build.save()
82 def setLayers(self, bitbake, layers, targets): argument
98 # if we're using a remotely fetched version of bitbake add its git
100 if bitbake.giturl and bitbake.commit:
101 gitrepos[(bitbake.giturl, bitbake.commit)] = []
[all …]
/OK3568_Linux_fs/yocto/poky/meta/lib/oeqa/buildperf/
H A Dtest_basic.py22 self.measure_cmd_resources(['bitbake', self.build_target], 'build',
23 'bitbake ' + self.build_target, save_bs=True)
34 self.run_cmd(['bitbake', self.build_target])
35 self.run_cmd(['bitbake', self.build_target, '-c', 'cleansstate'])
38 self.measure_cmd_resources(['bitbake', self.build_target], 'build',
39 'bitbake ' + self.build_target)
55 cmd = ['bitbake', '-R', postfile, self.build_target]
57 'bitbake' + self.build_target,
68 self.run_cmd(['bitbake', self.build_target])
73 cmd = ['bitbake', self.build_target, '-c', 'rootfs']
[all …]
/OK3568_Linux_fs/yocto/poky/documentation/migration-guides/
H A Drelease-notes-3.4.1.rst24 - bitbake.conf: Fix corruption of GNOME mirror url
25 - bitbake.conf: Use wayland distro feature for native builds
26 - bitbake: Revert "parse/ast: Show errors for append/prepend/remove operators combined with +=/.="
27 - bitbake: bitbake-worker: Add debug when unpickle fails
28 - bitbake: cooker: Fix task-depends.dot for multiconfig targets
29 - bitbake: cooker: Handle parse threads disappearing to avoid hangs
30 - bitbake: cooker: Handle parsing results queue race
31 - bitbake: cooker: Remove debug code, oops :(
32 - bitbake: cooker: check if upstream hash equivalence server is available
33 - bitbake: fetch/git: Handle github dropping git:// support
[all …]
H A Drelease-notes-4.0.4.rst31 - bitbake.conf: set BB_DEFAULT_UMASK using ??=
32 - bitbake: ConfHandler/BBHandler: Improve comment error messages and add tests
33 - bitbake: ConfHandler: Remove lingering close
34 - bitbake: bb/utils: movefile: use the logger for printing
35 - bitbake: bb/utils: remove: check the path again the expand python glob
36 - bitbake: bitbake-user-manual: Correct description of the ??= operator
37 - bitbake: bitbake-user-manual: npm fetcher: improve description of SRC_URI format
38 - bitbake: bitbake: bitbake-user-manual: hashserv can be accessed on a dedicated domain
39 - bitbake: bitbake: runqueue: add cpu/io pressure regulation
40 - bitbake: bitbake: runqueue: add memory pressure regulation
[all …]
H A Drelease-notes-4.0.5.rst19 - bitbake: Fix npm to use https rather than http
20 - bitbake: asyncrpc/client: Fix unix domain socket chdir race issues
21 - bitbake: bitbake: Add copyright headers where missing
22 - bitbake: gitsm: Error out if submodule refers to parent repo
23 - bitbake: runqueue: Drop deadlock breaking force fail
24 - bitbake: runqueue: Ensure deferred tasks are sorted by multiconfig
25 - bitbake: runqueue: Improve deadlock warning messages
26 - bitbake: siggen: Fix insufficent entropy in sigtask file names
27 - bitbake: tests/fetch: Allow handling of a file:// url within a submodule
33 - dev-manual: fix reference to BitBake user manual
[all …]
/OK3568_Linux_fs/yocto/poky/bitbake/
H A DREADME1 Bitbake
4 BitBake is a generic task execution engine that allows shell and Python tasks to be run
6 One of BitBake's main users, OpenEmbedded, takes this core and builds embedded Linux software
9 For information about Bitbake, see the OpenEmbedded website:
12 Bitbake plain documentation can be found under the doc directory or its integrated
22 for OpenEmbedded (and its core) not bitbake patches (bitbake-devel@lists.openembedded.org)
27 git send-email -M -1 --to bitbake-devel@lists.openembedded.org
31 https://lists.openembedded.org/g/bitbake-devel
35 https://git.openembedded.org/bitbake/
39 Bitbake has a testsuite located in lib/bb/tests/ whichs aim to try and prevent regressions.
[all …]
H A DChangeLog1 Changes in Bitbake 1.9.x:
22 (requires new FETCHCMD_svn definition in bitbake.conf)
43 - Fix/improve bitbake -s output
116 the way bitbake schedules tasks
153 whitelisted variables into the data store. If BB_PRESERVE_ENV is set bitbake will use
155 used instead of the internal bitbake one. Alternatively, BB_ENV_EXTRAWHITE can be used
162 - Add tryaltconfigs option to control whether bitbake trys using alternative providers
182 Changes in Bitbake 1.8.0:
185 Changes in BitBake 1.7.x:
187 of tasks. Code from bin/bitbake replaced with runqueue.py
[all …]
/OK3568_Linux_fs/yocto/poky/documentation/test-manual/
H A Dintro.rst122 $ bitbake image -c testsdkext
132 $ bitbake image -c testimage
152 $ bitbake image -c testsdk
158 through :ref:`bitbake-selftest <ref-manual/release-process:Testing and Quality Assurance>` and
171 - *bitbake-selftest:*
173 These tests are self-contained and test BitBake as well as its APIs,
175 ``bitbake/lib/*/tests``.
177 From within the BitBake repository, run the following::
179 $ bitbake-selftest
182 variable when running "bitbake-selftest" as follows::
[all …]
/OK3568_Linux_fs/yocto/poky/scripts/
H A Doe-find-native-sysroot41 echo "Running bitbake -e $1"
42 BITBAKE_E="`bitbake -e $1`"
46 # This indicates that there was an error running bitbake -e that
48 echo "There was an error running bitbake to determine STAGING_DIR_NATIVE"
49 echo "Here is the output from bitbake -e $1"
56 BITBAKE=`which bitbake 2> /dev/null`
57 if [ "x$BITBAKE" != "x" ]; then
59 # Root cannot run bitbake unless sanity checking is disabled
61 …echo "Error: root cannot run bitbake by default, and I cannot find a ./conf directory to be able t…
71 echo "Error: Unable to locate bitbake command."
[all …]
H A Dtest-reexec18 targets=`bitbake -s | cut -d " " -f 1`
28 sstate_dir=`bitbake $target -e | grep "^SSTATE_DIR=" | cut -d "\"" -f 2`
29 sstate_pkgspec=`bitbake $target -e | grep "^SSTATE_PKGSPEC=" | cut -d "\"" -f 2`
30 sstasks=`bitbake $target -e | grep "^SSTATETASKS=" | cut -d "\"" -f 2`
77 bitbake $target -c cleansstate > $LOGS/initial.$target.$task
78 bitbake $target >> $LOGS/initial.$target.$task
81 bitbake $target -c $task -f > $LOGS/force.$target.$task
85 bitbake $target -c clean > $LOGS/clean.$target.$task
87 bitbake $target >> $LOGS/force.$target.$task
91 bitbake $target -c clean > $LOGS/clean.$target.$task
[all …]
/OK3568_Linux_fs/yocto/poky/documentation/overview-manual/
H A Dconcepts.rst17 The :term:`BitBake` task executor
23 BitBake handles the parsing and execution of the data files. The data
35 BitBake knows how to combine multiple data sources together and refers
46 BitBake section in Yocto Project Components
49 BitBake is the tool at the heart of the :term:`OpenEmbedded Build System`
54 This section briefly introduces BitBake. If you want more information on
55 BitBake, see the :doc:`BitBake User Manual <bitbake:index>`.
57 To see a list of the options BitBake supports, use either of the
60 $ bitbake -h
61 $ bitbake --help
[all …]
/OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/tests/
H A Drunqueue.py2 # BitBake Tests for runqueue task processing
56 cmd = ["bitbake", "a1"]
66 cmd = ["bitbake", "a1"]
78 cmd = ["bitbake", "a1"]
89 cmd = ["bitbake", "a1"]
100 cmd = ["bitbake", "a1"]
111 cmd = ["bitbake", "a1", "-c", "patch"]
121 cmd = ["bitbake", "a1:do_patch", "a1:do_populate_sysroot"]
132 cmd = ["bitbake", "c1:do_patch", "a1"]
146 cmd = ["bitbake", "a1"]
[all …]

12345678910>>...22