<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/buildman/control.py, branch v2020.04</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/buildman/control.py?h=v2020.04</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/buildman/control.py?h=v2020.04'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2019-12-11T04:11:31Z</updated>
<entry>
<title>buildman: Add options to get the arch and toolchain info</title>
<updated>2019-12-11T04:11:31Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-12-05T22:59:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=57cb9d52397c9051d7b3d27bd107cce04a16846f'/>
<id>urn:sha1:57cb9d52397c9051d7b3d27bd107cce04a16846f</id>
<content type='text'>
Sometimes it is useful for external tools to use buildman to provide the
toolchain information. Add an -a option which shows the value to use for
the ARCH environment variable, and -A which does the same for
CROSS_COMPILE

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Figure out boards before commits</title>
<updated>2019-12-11T04:11:31Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-12-05T22:59:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7c66ead45267122c48bc854d1d5bd0d9a99bf943'/>
<id>urn:sha1:7c66ead45267122c48bc854d1d5bd0d9a99bf943</id>
<content type='text'>
At present buildman looks at toolchains, then commits and then boards.
Move the board processing up above the commit processing, since it relates
to the toolchain code. This will make it easier to check the toolchains
needed for a board without processing commits first.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Ask genboardscfg to be quiet</title>
<updated>2019-12-11T04:11:31Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-12-05T22:59:12Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6a3fc91ea7fdf3f6e35c92eb02c9c73fb9f42d04'/>
<id>urn:sha1:6a3fc91ea7fdf3f6e35c92eb02c9c73fb9f42d04</id>
<content type='text'>
Now that this tool has a 'quiet' flag, use it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Fix problem with non-existent output directories</title>
<updated>2019-11-23T19:53:48Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2019-11-19T20:14:33Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=70f681398521c2ec2a75f612c04c506a0696c3b9'/>
<id>urn:sha1:70f681398521c2ec2a75f612c04c506a0696c3b9</id>
<content type='text'>
Now that we have buildman telling genboards.cfg to use an output
directory we need to ensure that it exists.

Cc: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Cc: Simon Glass &lt;sjg@chromium.org&gt;
Fixes: bc750bca1246 ("tools: buildman: Honor output directory when generating boards.cfg")
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>buildman: Convert to Python 3</title>
<updated>2019-11-05T01:15:32Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-10-31T13:42:53Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c05aa0364280803d8274e260a739553d588ea052'/>
<id>urn:sha1:c05aa0364280803d8274e260a739553d588ea052</id>
<content type='text'>
Convert buildman to Python 3 and make it use that, to meet the 2020
deadline.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>tools: buildman: Honor output directory when generating boards.cfg</title>
<updated>2019-10-29T20:17:36Z</updated>
<author>
<name>Bin Meng</name>
<email>bmeng.cn@gmail.com</email>
</author>
<published>2019-10-28T14:24:59Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bc750bca1246de09ca653141c1add7e10c04a37c'/>
<id>urn:sha1:bc750bca1246de09ca653141c1add7e10c04a37c</id>
<content type='text'>
buildman always generates boards.cfg in the U-Boot source tree.
When '-o' is given, we should generate boards.cfg to the given
output directory.

Signed-off-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: fix typo</title>
<updated>2019-02-09T19:50:22Z</updated>
<author>
<name>Chris Packham</name>
<email>judge.packham@gmail.com</email>
</author>
<published>2019-01-18T07:40:29Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=58804b8cf291c56eee9fbfbfdb7c10e8a238444b'/>
<id>urn:sha1:58804b8cf291c56eee9fbfbfdb7c10e8a238444b</id>
<content type='text'>
Fix a typo in the error message from CheckOutputDir().

Signed-off-by: Chris Packham &lt;judge.packham@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Add support for building with clang</title>
<updated>2019-01-15T00:47:13Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-01-07T23:44:20Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=00beb2485f71ab23114b37ef47d136e269ef69f7'/>
<id>urn:sha1:00beb2485f71ab23114b37ef47d136e269ef69f7</id>
<content type='text'>
Add a -O option which allows building with clang.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Only print toolchain probing with -v</title>
<updated>2018-11-21T02:14:22Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2018-11-06T23:02:10Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=40232c91d70f4f2066408cabf1afba1deb190df6'/>
<id>urn:sha1:40232c91d70f4f2066408cabf1afba1deb190df6</id>
<content type='text'>
At present --list-tool-chains prints a lot of information about the
toolchain-probing process. This is generally not very interesting.
Update buildman to print this only if --list-tool-chains is given
with -v.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Add a --boards option to specify particular boards to build</title>
<updated>2018-11-14T17:16:27Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2018-06-12T05:26:46Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0689036a35296a3d51685a0b671f805818f94af7'/>
<id>urn:sha1:0689036a35296a3d51685a0b671f805818f94af7</id>
<content type='text'>
At present 'buildman sandbox' will build all 5 boards for the sandbox
architecture rather than the single board 'sandbox'. The only current way
to exclude sandbox_spl, sandbox_noblk, etc. is to use -x which is a bit
clumbsy.

Add a --boards option to allow individual build targets to be specified.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
