From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/11] buildman: Make the tool friendlier for first-time users
Date: Thu, 7 Jul 2016 12:27:53 -0600 [thread overview]
Message-ID: <577E9F29.20301@wwwdotorg.org> (raw)
In-Reply-To: <1467580467-19186-1-git-send-email-sjg@chromium.org>
On 07/03/2016 03:14 PM, Simon Glass wrote:
> This makes a few minor improvements to buildman to make it work more easiler
> for first-time users:
>
> - Improve progress and warning messages when fetching toolchains
> - Fix a bug where toolchain paths can be overwritten when fetching
> - Note at the top of the help how to get started
>
> Also this series removes MAKEALL. Since buildman has been around for 3 years
> it may be time to do this. If not, we can leave it for now.
Sounds great:-)
BTW, one problem I've come across with buildman recently is that it
re-orders warnings/errors from the compiler. In particular, it seems to
separate what it thinks are warning from errors (perhaps stdout/stderr
split??) but I'm not sure it always gets it right, and I think elides
duplicate lines when doing so. When running buildman repeatedly while
doing development, and experiencing a compile error, this makes it
extremely difficult to interpret some of the compiler's multi-line
messages. Is it possible to have an option that turns off all the output
processing, and just shows stderr/out mixed up as they would appear
"interactively" when manually invoked from a shell, with no
post-processing? Occasionally I have to fall back to a manual "make"
invocation due to this.
next prev parent reply other threads:[~2016-07-07 18:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 21:14 [U-Boot] [PATCH 00/11] buildman: Make the tool friendlier for first-time users Simon Glass
2016-07-03 21:14 ` [U-Boot] [PATCH 01/11] buildman: Tidy up the README a little Simon Glass
2016-07-08 14:27 ` Tom Rini
2016-07-03 21:14 ` [U-Boot] [PATCH 02/11] buildman: Automatically create a config file if needed Simon Glass
2016-07-07 18:15 ` Stephen Warren
2016-07-03 21:14 ` [U-Boot] [PATCH 03/11] buildman: Fix the 'help' test to use the correct path Simon Glass
2016-07-03 21:14 ` [U-Boot] [PATCH 04/11] buildman: Allow the toolchain error to be suppressed Simon Glass
2016-07-07 18:17 ` Stephen Warren
2016-07-03 21:14 ` [U-Boot] [PATCH 05/11] buildman: Improve the toolchain progress/error output Simon Glass
2016-07-08 14:27 ` Tom Rini
2016-07-03 21:14 ` [U-Boot] [PATCH 06/11] buildman: Fix a typo in TestSettingsHasPath() Simon Glass
2016-07-03 21:14 ` [U-Boot] [PATCH 07/11] buildman: Drop the toolchain error when downloading toolchains Simon Glass
2016-07-03 21:14 ` [U-Boot] [PATCH 08/11] buildman: Avoid overwriting existing toolchain entries Simon Glass
2016-07-07 18:21 ` Stephen Warren
2016-07-08 14:27 ` Tom Rini
2016-07-03 21:14 ` [U-Boot] [PATCH 09/11] buildman: Add a quick-start note Simon Glass
2016-07-07 18:23 ` Stephen Warren
2016-07-08 14:27 ` Tom Rini
2016-07-03 21:14 ` [U-Boot] [PATCH 10/11] Drop the MAKEALL tool Simon Glass
2016-07-08 14:27 ` Tom Rini
2016-07-03 21:14 ` [U-Boot] [PATCH 11/11] Drop references to MAKEALL in the documentation Simon Glass
2016-07-08 14:27 ` Tom Rini
2016-07-07 18:27 ` Stephen Warren [this message]
2016-07-08 14:27 ` [U-Boot] [PATCH 00/11] buildman: Make the tool friendlier for first-time users Tom Rini
2016-07-08 14:26 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=577E9F29.20301@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox