<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/buildman/cmdline.py, branch v2022.10</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/buildman/cmdline.py?h=v2022.10</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/buildman/cmdline.py?h=v2022.10'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2022-08-05T15:47:56Z</updated>
<entry>
<title>buildman: Incorporate the genboardscfg.py tool</title>
<updated>2022-08-05T15:47:56Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2022-07-12T01:04:04Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a8a0141bc2c15fafd5afc96a089e9b2c6a0df340'/>
<id>urn:sha1:a8a0141bc2c15fafd5afc96a089e9b2c6a0df340</id>
<content type='text'>
Bring this tool into buildman, so we don't have to run it separately. The
board.cfg file is still produced as part of the build, to save time when
doing another build in the same working directory. If it is out of date
with respect to the Kconfig, it is updated.

Time to regenerate on a recent single-thread machine is 4.6s (1.3s on a
32-thread machine), so we do need some sort of cache if we want buildman
to be useful on incremental builds. We could use Python's pickle format
but:

- it seems useful to allow boards.cfg to be regenerated, at least for a
  while, in case other tools use it
- it is possible to grep the file easily, e.g. to find boards which use
  a particular SoC (similar to 'buildman -nv &lt;soc&gt;'

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Suggested-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>buildman: Support running from an IDE</title>
<updated>2022-08-05T15:47:55Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2022-07-12T01:03:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ae1a09f8039a064135629e3b37e108e8ee1814b3'/>
<id>urn:sha1:ae1a09f8039a064135629e3b37e108e8ee1814b3</id>
<content type='text'>
Add a flag to allow buildman to behave properly for use from an IDE. This
shows error/warning output on stderr and drops all summary and progress
information.

This should normally only be used when building a single board.

Fix up a confusing comment for GetResultSummary() while we are here, since
we want to use the Outcome object to access the unprocessed error lines
from the build.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Drop -I option</title>
<updated>2022-08-05T15:47:55Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2022-07-12T01:03:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5635c5072062eb988ff60385ad9b93526d22ce7c'/>
<id>urn:sha1:5635c5072062eb988ff60385ad9b93526d22ce7c</id>
<content type='text'>
This has been deprecated with a notice that it will be removed after April
2021. Drop it now.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Allow adjusting board config on the fly</title>
<updated>2022-02-09T04:07:59Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2022-01-22T12:07:33Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2b4806e481026df7364cb9ed53ffc577e3dc59bb'/>
<id>urn:sha1:2b4806e481026df7364cb9ed53ffc577e3dc59bb</id>
<content type='text'>
Add a -a option to specify changes to the config before the build
commences. For example

   buildman -a ~CONFIG_CMDLINE

disables CONFIG_CMDLINE before doing the build.

This makes it easier to try things out as well as to write tests without
creating a new board or manually manging the .config file.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Add a flag to control the traceback</title>
<updated>2022-02-09T04:07:59Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2022-01-22T12:07:29Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=433fa549e138a06085fe3a9a0ac4924bb1804687'/>
<id>urn:sha1:433fa549e138a06085fe3a9a0ac4924bb1804687</id>
<content type='text'>
At present the full horror of the Python traceback is shown by default. It
is normally only useful for debugging. Turn it off by default and add a
--debug flag to enable it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Support single-threaded operation</title>
<updated>2021-03-04T22:51:43Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-01-31T05:17:46Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=b82492bbccb0ecdee17108ed43c4220f00f3f4f3'/>
<id>urn:sha1:b82492bbccb0ecdee17108ed43c4220f00f3f4f3</id>
<content type='text'>
At present even if only a single thread is in use, buildman still uses
threading.

For some debugging it is helpful to do everything in the main process.
Allow -T0 to support this.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Make sure that -o is given with -w</title>
<updated>2020-04-26T20:24:08Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-04-17T23:51:32Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=88daaef19f985b6ba2f9c0f62eed5378d6d40ebd'/>
<id>urn:sha1:88daaef19f985b6ba2f9c0f62eed5378d6d40ebd</id>
<content type='text'>
It is a bad idea to use the default output directory ('..') with -w since
it does a build in that directory and writes various files these.

Require that -o is given to avoid this problem.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Add an option to ignore migration warnings</title>
<updated>2020-04-21T12:33:47Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-04-09T21:08:53Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=113a8a5ff3c44637ebfc661b6c399d39bcb4c180'/>
<id>urn:sha1:113a8a5ff3c44637ebfc661b6c399d39bcb4c180</id>
<content type='text'>
These are becoming more common now. They cause boards to show warnings
which can be mistaking for compiler warnings.

Add a buildman option to ignore them. This option works only with the
summary option (-s). It does not affect the build process.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Add an option to ignore device-tree warnings</title>
<updated>2020-04-21T12:33:47Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-04-09T21:08:52Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=174592b964c762eca5e405494dda0ffc10deeb7b'/>
<id>urn:sha1:174592b964c762eca5e405494dda0ffc10deeb7b</id>
<content type='text'>
Unfortunately the plague of device-tree warnings has not lifted. These
warnings infiltrate almost every build, adding noise and confusion.

Add a buildman option to ignore them. This option works only with the
summary option (-s). It does not affect the build process.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Make -I the default</title>
<updated>2020-04-21T12:33:47Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-04-09T21:08:51Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=eb70a2c0598c416777049a89c09c32474ff918b0'/>
<id>urn:sha1:eb70a2c0598c416777049a89c09c32474ff918b0</id>
<content type='text'>
At present buildman defaults to running 'mrproper' on every thread before
it starts building commits for each board. This can add a delay of about 5
seconds to the start of the process, since the tools and other invariants
must be rebuilt.

In particular, a build without '-b', to build current source, runs much
slower without -I, since any existing build is removed, thus losing the
possibility of an incremental build.

Partly this behaviour was to avoid strange build-system problems caused by
running 'make defconfig' for one board and then one with a different
architecture. But these problems were fixed quite a while ago.

The -I option (which disabled mrproper) was introduced four years ago and
does not seem to cause any problems with builds.

So make -I the default and deprecate the option. To allow use of
'mrproper', add a new -m flag.

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