summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/Process/minidump/ProcessMinidump.cpp
diff options
context:
space:
mode:
authorDiana Picus <diana.picus@linaro.org>2019-02-11 10:30:22 +0000
committerDiana Picus <diana.picus@linaro.org>2019-02-11 10:30:22 +0000
commit2d29cc311be98ad9600a67a868464462f59b917c (patch)
treeb88f573efe071df36f5060144c595ce1110e0767 /lldb/source/Plugins/Process/minidump/ProcessMinidump.cpp
parent0e04ebdcda44ef90e25abd0a2e65cc755ae8bc37 (diff)
downloadbcm5719-llvm-2d29cc311be98ad9600a67a868464462f59b917c.tar.gz
bcm5719-llvm-2d29cc311be98ad9600a67a868464462f59b917c.zip
test-release.sh: Add option to use ninja
Allow the use of ninja instead of make. This is useful on some platforms where we'd like to be able to limit the number of link jobs without slowing down the other steps of the release. This patch adds a -use-ninja command line option, which sets the generator to Ninja both for LLVM and the test-suite. It also deals with some differences between make and ninja: * DESTDIR handling - ninja doesn't like this to be listed after the target, but both make and ninja can handle it before the command * Verbose mode - ninja uses -v, make uses VERBOSE=1 * Keep going mode - make has a -k mode, which builds as much as possible even when failures are encountered; for ninja we need to set a hard limit (we use 100 since most people won't look at 100 failures anyway) I haven't tested with gmake. llvm-svn: 353685
Diffstat (limited to 'lldb/source/Plugins/Process/minidump/ProcessMinidump.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud