Lines Matching refs:build
11 If you just want to quickly set up buildman so you can build something (for
26 with your patch series. It can build each individual commit and report
58 directories, which you can look at while the build is progressing, or when
61 Buildman is designed to build entire git branches, i.e. muliple commits. It
64 commit). It is possible to build a branch for one board, then later build it
65 for another board. If you want buildman to re-build a commit it has already
80 incremental build. Eventually the thread reaches the last commit and stops.
82 after every commit, and your build will be very slow. This is because a
84 incremental build.
101 builds the upstream commit as well, for comparison. It cannot build
107 If you just want to build the current source tree, leave off the -b flag
110 source has changed, and will build all specified boards in this case.
119 Buildman lets you build all boards, or a subset. Specify the subset by passing
140 means to build all arm boards except nvidia, freescale and anything ending
147 the binary output into a directory when a build is successful. Size
189 to build x86 commits.
513 Total boards to build for each commit: 1059
515 This shows that it will build all 1059 boards, using 4 threads (because
529 To run the build for real, take off the -n:
540 has managed to successfully build 528. Another 36 have built with warnings,
541 and 124 more didn't build at all. Buildman expects to complete the process
545 To find out how the build went, ask for a summary with -s. You can do this
546 either before the build completes (presumably in another terminal) or
573 the build is still in progress so many boards are not built yet (use -u to
593 +make: *** [/u-boot/lcd9b/.bm-work/00/build/u-boot] Error 139
625 The full build output in this case is available in:
629 done: Indicates the build was done, and holds the return code from make.
630 This is 0 for a good build, typically 2 for a failure.
635 in silent mode. Use -V to force a verbose build (this passes V=1
638 toolchain: Shows information about the toolchain used for the build.
642 It is possible to get the build binary output there also. Use the -k option
680 build fails so we don't get code size numbers. The numbers are fractional
693 for an overview of how your entire series affects code size. It will build
848 also allows build flags to be passed to 'make'. It consists of several
876 U-Boot's build system supports a few flags (such as BUILD_TAG) which
877 affect the build product. These flags can be specified in the buildman
896 Note that you can pass ad-hoc options to the build using environment
907 build the selected boards and display build status as it runs (i.e. -v is
914 You can build a range of commits by specifying a range instead of a branch
919 will build commits in us-buildman that are not in upstream/master.
927 trust the build system's incremental build capabilities, you can pass the -I
929 work 'make' does, and hence speed up the build. This flag will speed up any
930 buildman invocation, since it reduces the amount of work done on any build.
932 One possible application of buildman is as part of a continual edit, build,
933 edit, build, ... cycle; repeatedly applying buildman to the same change or
936 modifications. In this scenario, buildman's default choice of build directory
937 causes more build work to be performed than strictly necessary.
944 rebuilds would not happen, thus allowing the build to operate as efficiently as
945 the build system and source changes allow. buildman's -P flag may be used to
948 build directory.
950 U-Boot's build system embeds information such as a build timestamp into the
969 Buildman supports this with the -K option, used after a build. This shows
995 files which are produced by a build. If all you want is to check the
996 configuration you can in fact avoid doing a full build, using -D. This tells
998 build the source. This is 5-10 times faster than doing a full build.
1034 - We don't want to maintain two build systems
1045 To build the current source tree, run buildman without a -b flag:
1047 ./tools/buildman/buildman <list of things to build>
1049 This will build the current source tree for the given boards and display
1055 ./tools/buildman/buildman -b <branch_name> <list of things to build>
1059 ./tools/buildman/buildman -b <branch_name> -s <list of things to build>
1061 to see the results of the build. Rather than showing you all the output,
1066 If you really want to see build results as they happen, use -v when doing a
1067 build (and -e to see the errors/warnings too).
1071 add commits, etc. without affecting the build in progress.
1073 The <list of things to build> can include board names, architectures or the
1078 - build all Power Architecture boards:
1083 - build all PowerPC boards manufactured by vendor "esd":
1086 - build all PowerPC boards manufactured either by "keymile" or "siemens":
1089 - build all Freescale boards with MPC83xx CPUs, plus all 4xx boards:
1106 to remove the build directory (normally ../<branch_name>) to run buildman
1121 --step 0 will build just the upstream commit and the last commit of your
1143 the build speed by building all commits for a board instead of the other