linux/poky.git/bitbake/doc, branch yocto-2.6Mirror of git.yoctoproject.org/pokyhttps://git.enea.com/cgit/linux/poky.git/atom?h=yocto-2.62018-10-29T16:54:48+00:00bitbake: bitbake-user-manual: Updates to variable wildcard support.2018-10-29T16:54:48+00:00Scott Rifenbarksrifenbark@gmail.com2018-10-24T23:11:03+00:00urn:sha1:2520246d6781f40e3d1aab13abb5a01dd09a7594
Fixes [YOCTO #12390]
Applied some fixes to the variable wildcard support documentation
in the BitBake manual. Wording changes and changes to make links
referencing Python syntax go to version 3 rather than version 2.
(Bitbake rev: 0cfc71d1a342b82781b0ba547421e41f6340902a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-user-manual: Added wildcarding descriptions2018-10-29T16:54:48+00:00Scott Rifenbarksrifenbark@gmail.com2018-10-18T20:15:49+00:00urn:sha1:8c0a94129e0e1699cd72fd965ac1cc6504b1269f
Fixes [YOCTO #12390]
Added specific descriptions for how wildcarding works for a variety
of variables and files (e.g. append files).
(Bitbake rev: 0a4377cb1837ede213d9640344f4908de3689d91)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-user-manual: fix description of BB_RUNTASK2018-10-18T09:59:27+00:00Chris Laplante via bitbake-develbitbake-devel@lists.openembedded.org2018-10-04T17:21:38+00:00urn:sha1:76361c9b389d3461962a7f82e78888a6f5de80bd
Contrary to what the manual said, BB_RUNTASK does include the do_
prefix, unlike BB_CURRENTTASK.
(Bitbake rev: 3f4968c77129252e8d0833fbd683372fca243a90)
Signed-off-by: Chris Laplante <chris.laplante@agilent.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: data: Fix whitespace on _remove operations2018-10-18T09:59:26+00:00Richard Purdierichard.purdie@linuxfoundation.org2018-10-16T13:16:27+00:00urn:sha1:a9aa1d24c7c4518173f622a1fab55a98a16150f9
We have some slightly odd behaviours with the current implementation of
_remove operations. For example:
TEST = " A B"
TEST_remove = "C"
would trigger TEST to become "A B" even thought it doesn't contain "C".
In particular, this means that an inactive remove operator added in a
bbappend could change the task checksum which is not desireable.
Fix the operation to preserve whitespace, adding new tests to make this
explict and test further corner cases. Also update the manual to match.
(Bitbake rev: c0a23dd9155c50a6b7df796980bc7b612cac7994)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-user-manual: Added section on multicong dependencies2018-10-04T13:33:31+00:00Scott Rifenbarksrifenbark@gmail.com2018-09-05T17:40:13+00:00urn:sha1:6e9ff843fdba084b7c50d95c3ff482ddb4f18e55
Created a new section to show how to handle dependencies when
you are doing a multiple configuration build. Put it in the
"Examples" section.
(Bitbake rev: fa42212a6cb7b64add4d6ca0f723a95c908c6b87)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-user-manual: Added BBMULTICONFIG support2018-10-04T13:33:31+00:00Scott Rifenbarksrifenbark@gmail.com2018-09-05T16:31:24+00:00urn:sha1:859d36b1309ccb41d0218bfad11c4cfceebcd980
The BBMULTICONFIG variable is a variable used for BitBake and was
not documented in the BitBake Manual glossary. I added the
definition. I also added the variable to the example in the section
describing how to execute builds for multiple configurations.
(Bitbake rev: 836f994ec530ba82c935cb41e006d1f128885dc2)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-user-manual: Added new section on multiconfig builds2018-10-04T13:33:31+00:00Scott Rifenbarksrifenbark@gmail.com2018-08-30T18:29:12+00:00urn:sha1:e06421bfc401c3aeac01db08e32c7833085352ec
Created a new example. Also added a figure for the separate
configuration file hierarchy
(Bitbake rev: f2d432674b187685591f60cec3b2980b377c63fe)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-user-manual: Added "number_threads" varflag2018-06-19T16:09:17+00:00Scott Rifenbarksrifenbark@gmail.com2018-06-18T22:06:16+00:00urn:sha1:d05a268c5069c3fb47ceed47862ba36b5f49ebd3
You can now limit on a task-specific basis the number of threads
a task will use. This is useful for machines that have high
numbers of cores and need to be rate-limited due to various
resource constraints.
(Bitbake rev: 4937ed392fdc4442dd91f644f329dda29f27242c)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-user-manual: Updated copyright year on title page to 20182018-05-24T16:17:25+00:00Scott Rifenbarksrifenbark@gmail.com2018-05-18T22:49:14+00:00urn:sha1:d886fa118c930d0e551f2a0ed02b35d08617f746
(Bitbake rev: 7799b17e7ac748e3639e5ab1e59b9b9c2a047bf6)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-user-manual: Updated "Task Checksums and Setscene" section2018-04-12T21:25:17+00:00Scott Rifenbarksrifenbark@gmail.com2018-04-12T19:55:29+00:00urn:sha1:8dbf71b553b3fb3063ab5f61bb3454a6ab8e6c08
Fixes [#YOCTO 12030]
Updated the "Task Checksums and Setscene" section to provide a bit
of user information around the bitbake-dumpsigs use that lets a
user examine signatures and inputs that determine if a do_compile
task is indeed supposed to be run.
Added more explanation of how a user can examine signatures used
to determine if a do_compile task is indeed supposed to be run.
(Bitbake rev: 103bbc6642261cd5da038ba2071621919ee01253)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>