<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml, branch 2.7_M2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=2.7_M2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=2.7_M2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2018-12-27T13:08:30+00:00</updated>
<entry>
<title>bitbake: bitbake-user-manual: Created unique tags for glossary variables.</title>
<updated>2018-12-27T13:08:30+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2018-12-27T00:22:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8615d47a3a39e78fb7cf29ee92203d18a2439a3b'/>
<id>urn:sha1:8615d47a3a39e78fb7cf29ee92203d18a2439a3b</id>
<content type='text'>
Fixes [YOCTO #12399]

The bug was to get the BitBake User Manual into the YP Mega-manual.
All the changes here create unique tags used with variables in the
BitBake Manual.  Prior to the fix, tags were identical between like
variables in the YP reference manual and the BitBake User Manual.
The reason for this is because when I created the BitBake manual's
glossary, it was a cut-and-paste operation to get the bulk of
the work started.  At the time, the BitBake User Manual was not
a part of the Mega-manual.  Once we decided to include the
BitBake User Manual as part of the Mega-Manual, building the
mega-manual produced warnings for all these duplicate links.

To fix, I have updated the variable tags in the BitBake User
Manual to use the following form:

   'var-bb-&lt;variable_name&gt;'

The tags used in the YP ref-manual follow this form (original):

   'var-&lt;variable_name&gt;'

(Bitbake rev: fb6de2057aae3fbdf37f007d2e47794b332020e1)

Signed-off-by: Scott Rifenbark &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-user-manual: Added hard-spacing to "_remove" example.</title>
<updated>2018-10-31T21:40:36+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2018-10-31T21:35:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=50614214097f90f53cedb1cd317098b025a57885'/>
<id>urn:sha1:50614214097f90f53cedb1cd317098b025a57885</id>
<content type='text'>
Rendering the manual to its HTML form was collapsing the two
leading and four trailing whitespace characters into single
whitespace characters.  I inserted multiple "&amp;nbsp;" strings
to force the spacing to come through.

(Bitbake rev: 701f76f773a6e77258f307a4f8e2ec1a8552f6f3)

Signed-off-by: Scott Rifenbark &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-user-manual: Updates to variable wildcard support.</title>
<updated>2018-10-29T16:54:48+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2018-10-24T23:11:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2520246d6781f40e3d1aab13abb5a01dd09a7594'/>
<id>urn:sha1:2520246d6781f40e3d1aab13abb5a01dd09a7594</id>
<content type='text'>
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 &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-user-manual: Added wildcarding descriptions</title>
<updated>2018-10-29T16:54:48+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2018-10-18T20:15:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8c0a94129e0e1699cd72fd965ac1cc6504b1269f'/>
<id>urn:sha1:8c0a94129e0e1699cd72fd965ac1cc6504b1269f</id>
<content type='text'>
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 &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: data: Fix whitespace on _remove operations</title>
<updated>2018-10-18T09:59:26+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2018-10-16T13:16:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a9aa1d24c7c4518173f622a1fab55a98a16150f9'/>
<id>urn:sha1:a9aa1d24c7c4518173f622a1fab55a98a16150f9</id>
<content type='text'>
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 &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-user-manual: Added "number_threads" varflag</title>
<updated>2018-06-19T16:09:17+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2018-06-18T22:06:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d05a268c5069c3fb47ceed47862ba36b5f49ebd3'/>
<id>urn:sha1:d05a268c5069c3fb47ceed47862ba36b5f49ebd3</id>
<content type='text'>
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 &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-user-manual: Updated "Task Checksums and Setscene" section</title>
<updated>2018-04-12T21:25:17+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2018-04-12T19:55:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8dbf71b553b3fb3063ab5f61bb3454a6ab8e6c08'/>
<id>urn:sha1:8dbf71b553b3fb3063ab5f61bb3454a6ab8e6c08</id>
<content type='text'>
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 &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-user-manual: Commented out Placeholder Paragraph</title>
<updated>2018-02-06T18:10:35+00:00</updated>
<author>
<name>Kristi Rifenbark</name>
<email>kristi@buzzcollectivemarketing.com</email>
</author>
<published>2018-02-02T20:24:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=44ea6ded0e8e73f5258ce55bd1b851e24243b76a'/>
<id>urn:sha1:44ea6ded0e8e73f5258ce55bd1b851e24243b76a</id>
<content type='text'>
Fixes [YOCTO #12030]

(Bitbake rev: b2642e4d5adc765b205e73fee65da679add33ed0)

Signed-off-by: Kristi Rifenbark &lt;kristi@buzzcollectivemarketing.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-user-manual: Updated "Events" for BuildStarted event</title>
<updated>2018-01-16T20:34:02+00:00</updated>
<author>
<name>Scott Rifenbark</name>
<email>srifenbark@gmail.com</email>
</author>
<published>2017-10-17T21:44:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ac6b9debadfe0bcb1d67b3ceef3148b71a8d77cd'/>
<id>urn:sha1:ac6b9debadfe0bcb1d67b3ceef3148b71a8d77cd</id>
<content type='text'>
BitBake now fires off one "BuildStarted" event per configuration when
it is configured for multiple configurations (multiconfig).  I updated
the bullet item for "bb.envent.BuildStarted()" to indicate that
behavior.

(Bitbake rev: 28720c85e64a56677b71d2170a0a07901d52b180)

Signed-off-by: Scott Rifenbark &lt;srifenbark@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-user-manual-metadata: include a space on a append example</title>
<updated>2017-10-07T22:20:41+00:00</updated>
<author>
<name>Leonardo Sandoval</name>
<email>leonardo.sandoval.gonzalez@linux.intel.com</email>
</author>
<published>2017-10-06T15:10:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a667a8512691735b554029e53aa694d1f63786c3'/>
<id>urn:sha1:a667a8512691735b554029e53aa694d1f63786c3</id>
<content type='text'>
By definition, the override operator "_append" does not include a space,
so include it.

(Bitbake rev: 6775e2de9067d8f472d7bfb5b78ec835a5688755)

Signed-off-by: Leonardo Sandoval &lt;leonardo.sandoval.gonzalez@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
