All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	Simon Glass <sjg@chromium.org>
Subject: [PATCH v5 06/16] buildman: Drop mention of MAKEALL
Date: Wed,  9 Nov 2022 19:14:44 -0700	[thread overview]
Message-ID: <20221110021455.1004335-7-sjg@chromium.org> (raw)
In-Reply-To: <20221110021455.1004335-1-sjg@chromium.org>

This script was removed about 6 years ago so most people should be aware
that it is not needed anymore. Drop mention of it.

Signed-off-by: Simon Glass <sjg@chromium.org>
---

(no changes since v3)

Changes in v3:
- Add new patch to drop mention of MAKEALL

 tools/buildman/buildman.rst | 110 ------------------------------------
 1 file changed, 110 deletions(-)

diff --git a/tools/buildman/buildman.rst b/tools/buildman/buildman.rst
index ae0b60648d9..d0b7bbd2b0d 100644
--- a/tools/buildman/buildman.rst
+++ b/tools/buildman/buildman.rst
@@ -3,8 +3,6 @@
 Buildman build tool
 ===================
 
-(Please read 'How to change from MAKEALL' if you are used to that tool)
-
 Quick-start
 -----------
 
@@ -1250,114 +1248,6 @@ latter number depends on the speed of your machine and the efficiency of the
 U-Boot build.
 
 
-How to change from MAKEALL
---------------------------
-
-Buildman includes most of the features of MAKEALL and is generally faster
-and easier to use. In particular it builds entire branches: if a particular
-commit introduces an error in a particular board, buildman can easily show
-you this, even if a later commit fixes that error.
-
-The reasons to deprecate MAKEALL are:
-- We don't want to maintain two build systems
-- Buildman is typically faster
-- Buildman has a lot more features
-
-But still, many people will be sad to lose MAKEALL. If you are used to
-MAKEALL, here are a few pointers.
-
-First you need to set up your tool chains - see the 'Setting up' section
-for details. Once you have your required toolchain(s) detected then you are
-ready to go.
-
-To build the current source tree, run buildman without a -b flag:
-
-.. code-block:: bash
-
-   ./tools/buildman/buildman <list of things to build>
-
-This will build the current source tree for the given boards and display
-the results and errors.
-
-However buildman usually works on entire branches, and for that you must
-specify a board flag:
-
-.. code-block:: bash
-
-   ./tools/buildman/buildman -b <branch_name> <list of things to build>
-
-followed by (afterwards, or perhaps concurrently in another terminal):
-
-.. code-block:: bash
-
-   ./tools/buildman/buildman -b <branch_name> -s <list of things to build>
-
-to see the results of the build. Rather than showing you all the output,
-buildman just shows a summary, with red indicating that a commit introduced
-an error and green indicating that a commit fixed an error. Use the -e
-flag to see the full errors and -l to see which boards caused which errors.
-
-If you really want to see build results as they happen, use -v when doing a
-build (and -e to see the errors/warnings too).
-
-You don't need to stick around on that branch while buildman is running. It
-checks out its own copy of the source code, so you can change branches,
-add commits, etc. without affecting the build in progress.
-
-The <list of things to build> can include board names, architectures or the
-like. There are no flags to disambiguate since ambiguities are rare. Using
-the examples from MAKEALL:
-
-Examples::
-
-  - build all Power Architecture boards:
-      MAKEALL -a powerpc
-      MAKEALL --arch powerpc
-      MAKEALL powerpc
-          ** buildman -b <branch> powerpc
-  - build all PowerPC boards manufactured by vendor "esd":
-      MAKEALL -a powerpc -v esd
-          ** buildman -b <branch> esd
-  - build all PowerPC boards manufactured either by "keymile" or "siemens":
-      MAKEALL -a powerpc -v keymile -v siemens
-          ** buildman -b <branch> keymile siemens
-  - build all Freescale boards with MPC83xx CPUs, plus all 4xx boards:
-      MAKEALL -c mpc83xx -v freescale 4xx
-          ** buildman -b <branch> mpc83xx freescale 4xx
-
-Buildman automatically tries to use all the CPUs in your machine. If you
-are building a lot of boards it will use one thread for every CPU core
-it detects in your machine. This is like MAKEALL's BUILD_NBUILDS option.
-You can use the -T flag to change the number of threads. If you are only
-building a few boards, buildman will automatically run make with the -j
-flag to increase the number of concurrent make tasks. It isn't normally
-that helpful to fiddle with this option, but if you use the BUILD_NCPUS
-option in MAKEALL then -j is the equivalent in buildman.
-
-Buildman puts its output in ../<branch_name> by default but you can change
-this with the -o option. Buildman normally does out-of-tree builds: use -i
-to disable that if you really want to. But be careful that once you have
-used -i you pollute buildman's copies of the source tree, and you will need
-to remove the build directory (normally ../<branch_name>) to run buildman
-in normal mode (without -i).
-
-Buildman doesn't keep the output result normally, but use the -k option to
-do this.
-
-Please read 'Theory of Operation' a few times as it will make a lot of
-things clearer.
-
-Some options you might like are::
-
-   -B shows which functions are growing/shrinking in which commit - great
-        for finding code bloat.
-   -S shows image sizes for each commit (just an overall summary)
-   -u shows boards that you haven't built yet
-   --step 0 will build just the upstream commit and the last commit of your
-        branch. This is often a quick sanity check that your branch doesn't
-        break anything. But note this does not check bisectability!
-
-
 Using boards.cfg
 ----------------
 
-- 
2.38.1.431.g37b22c650d-goog


  parent reply	other threads:[~2022-11-10  2:16 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  2:14 [PATCH v5 00/16] buildman: Correct various issues with missing blobs Simon Glass
2022-11-10  2:14 ` [PATCH v5 01/16] image: Correct strncpy() warning with image_set_name() Simon Glass
2022-11-23  2:12   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 02/16] Makefile: Correct the binman rule Simon Glass
2022-11-10  8:01   ` Pali Rohár
2022-11-10 20:40     ` Simon Glass
2022-11-23  2:11       ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 03/16] doc: Correct the path to the Makefile documentation Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 04/16] binman: Use an exit code when blobs are missing Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 05/16] buildman: Convert documentation to rST Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` Simon Glass [this message]
2022-11-23  2:11   ` [PATCH v5 06/16] buildman: Drop mention of MAKEALL Simon Glass
2022-11-10  2:14 ` [PATCH v5 07/16] buildman: Update the arc toolchain Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 08/16] buildman: Update the default settings file Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 09/16] buildman: Drop mention of old architectures Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 10/16] buildman: Detect binman reporting missing blobs Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-12-05 23:13   ` Peter Robinson
2022-12-05 23:23     ` Tom Rini
2022-12-05 23:29       ` Peter Robinson
2022-12-05 23:34         ` Tom Rini
2022-12-05 23:43           ` Peter Robinson
2022-12-05 23:46             ` Tom Rini
2022-12-05 23:49               ` Peter Robinson
2022-12-05 23:55               ` Simon Glass
2022-12-05 23:56                 ` Tom Rini
2022-12-05 23:57                   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 11/16] binman: Add a separate section about environment variables Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 12/16] global: Do not default to faking missing binaries for buildman Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 13/16] buildman: Ensure config_fname is inited Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 14/16] buildman: Reinstate removal of temp output dir in tests Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 15/16] buildman: Add --allow-missing flag to allow missing blobs Simon Glass
2022-11-23  2:11   ` Simon Glass
2022-11-10  2:14 ` [PATCH v5 16/16] binman: Add documentation for the command line args Simon Glass
2022-11-23  2:11   ` Simon Glass

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=20221110021455.1004335-7-sjg@chromium.org \
    --to=sjg@chromium.org \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=trini@konsulko.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.