Searched full:buildman (Results 1 – 25 of 26) sorted by relevance
12
/openbmc/u-boot/ |
H A D | .travis.yml | 43 # prepare buildman environment 44 - echo -e "[toolchain]\nroot = /usr" > ~/.buildman 45 - echo -e "arc = /tmp/arc_gnu_2018.09_prebuilt_uclibc_le_archs_linux_install" >> ~/.buildman 46 - echo -e "\n[toolchain-alias]\nsh = sh2\n" >> ~/.buildman 47 - cat ~/.buildman 70 - if [[ "${TOOLCHAIN}" == *m68k* ]]; then ./tools/buildman/buildman --fetch-arch m68k ; fi 71 …- if [[ "${TOOLCHAIN}" == *microblaze* ]]; then ./tools/buildman/buildman --fetch-arch microblaze … 72 - if [[ "${TOOLCHAIN}" == *mips* ]]; then ./tools/buildman/buildman --fetch-arch mips ; fi 73 - if [[ "${TOOLCHAIN}" == *sh* ]]; then ./tools/buildman/buildman --fetch-arch sh2 ; fi 75 ./tools/buildman/buildman --fetch-arch i386; [all …]
|
H A D | MAINTAINERS | 419 BUILDMAN 422 F: tools/buildman/
|
H A D | Kconfig | 240 make / buildman.
|
H A D | README | 3493 just run the buildman script (tools/buildman/buildman), which will 3495 will take a while. Please see the buildman README, or run 'buildman -H' 4975 * Before sending the patch, run the buildman script on your patched
|
/openbmc/u-boot/tools/buildman/ |
H A D | README | 9 If you just want to quickly set up buildman so you can build something (for 13 PATH=$PATH:`pwd`/tools/buildman 14 buildman --fetch-arch arm 15 buildman -k rpi_2 28 A key feature of buildman is its output summary, which allows warnings, 37 Buildman can be stopped and restarted, in which case it will continue 41 Buildman gets so tied up in its work that it can ignore the outside world. 52 Buildman is a builder. It is not make, although it runs make. It does not 59 Buildman is designed to build entire git branches, i.e. muliple commits. It 63 for another board. If you want buildman to re-build a commit it has already [all …]
|
H A D | bsettings.py | 10 """Set up the buildman settings module by reading config files 22 config_fname = '%s/.buildman' % os.getenv('HOME') 24 print 'No config file found ~/.buildman\nCreating one...\n' 71 print "Couldn't create buildman config file '%s'\n" % config_fname
|
H A D | func_test.py | 21 # Buildman settings file 55 buildman: refactor help message 57 "buildman [options]" is displayed by default. 73 This option is currently not supported, but needs to be, for buildman to 166 """Functional test for buildman. 168 This aims to test from just below the invocation of buildman (parsing 416 """Test that buildman aborts when there are no boards""" 422 """Very simple test to invoke buildman on the current source""" 440 # Buildman always builds the upstream commit as well
|
H A D | toolchain.py | 230 print ("Warning: No tool chains. Please run 'buildman " 232 "add a [toolchain] section to your buildman config file " 493 tmpdir = tempfile.mkdtemp('.buildman') 539 """Check if buildman will find this toolchain 575 dest = os.path.join(home, '.buildman-toolchains') 602 # Make sure that it will be found by buildman
|
H A D | control.py | 50 why_selected: Dictionary where each key is a buildman argument 112 """The main control code for buildman 236 # Conflicting tags are not a problem for buildman, since it does not use 237 # them. For example, Series-version is not useful for buildman. On the
|
H A D | test.py | 29 # Buildman settings file 107 """Test buildman 274 # The second line of errors[3] is a duplicate, so buildman will drop it 288 # The second line of errors[3] is a duplicate, so buildman will drop it 326 options.branch = 'test-buildman'
|
H A D | cmdline.py | 50 help='Path to buildman config file', default='') 76 help='Directory where all builds happen and buildman has its workspace (default is ../)')
|
H A D | builder.py | 34 Buildman works by keeping the machine as busy as possible, building different 58 The base directory used by buildman is normally '../<branch>', i.e. 66 Buildman also create working directories for each thread, in a .bm-work/ 156 a previous run of buildman) is marked as failed, rebuild it. 170 incremental building, where buildman reconfigures on the first 172 the following commits. In fact buildman will reconfigure and
|
H A D | builderthread.py | 209 # directory (i.e. the current directory where buildman
|
/openbmc/u-boot/test/ |
H A D | run | 45 run_test "buildman" ./tools/buildman/buildman -t ${skip}
|
/openbmc/u-boot/board/Barix/ipam390/ |
H A D | README.ipam390 | 34 run "tools/buildman/buildman -k ipam390" in the u-boot source tree. 74 $ tools/buildman/buildman -k ipam390
|
/openbmc/u-boot/doc/ |
H A D | README.m68k | 59 ./tools/buildman/buildman m68k
|
H A D | README.sha1 | 54 If you do a "buildman -k pcs440ep" or a "make all" to get the U-Boot image,
|
H A D | git-mailrc | 125 alias buildman uboot, sjg
|
H A D | README.log | 206 generated by 'buildman -S' for snow, which is a Thumb-2 board (all units in
|
/openbmc/u-boot/tools/ |
H A D | genboardscfg.py | 27 sys.path.insert(1, os.path.join(os.path.dirname(__file__), 'buildman'))
|
H A D | moveconfig.py | 110 the same tools as buildman, so see that tool for setup (e.g. --fetch-arch). 316 sys.path.append(os.path.join(os.path.dirname(__file__), 'buildman'))
|
/openbmc/u-boot/tools/binman/ |
H A D | README | 775 - Consider making binman work with buildman, although if it is used in the
|
/openbmc/ |
D | opengrok1.0.log | 2208 2025-03-15 03:00:41.766-0500 FINEST t473 IndexDatabase.setupDeletedUids: live doc: '/openbmc/u-boot/tools/buildman/builder.py' (558) at 20210308005003756 [all...] |
D | opengrok2.0.log | 2315 2025-03-14 03:00:45.204-0500 FINEST t563 IndexDatabase.setupDeletedUids: live doc: '/openbmc/u-boot/tools/buildman/builder.py' (558) at 20210308005003756 [all...] |
/openbmc/linux/ |
H A D | opengrok1.0.log | [all...] |
12