diff options
| author | Nico Weber <nicolasweber@gmx.de> | 2018-12-19 23:52:16 +0000 |
|---|---|---|
| committer | Nico Weber <nicolasweber@gmx.de> | 2018-12-19 23:52:16 +0000 |
| commit | 9bd5a4661cdfd11ae37dadc8758d27e4d9fd903c (patch) | |
| tree | 2dc6ab1a33c8e150cbbe65405f776d6507c0fc97 /lldb/packages/Python/lldbsuite/test/functionalities/expr-doesnt-deadlock | |
| parent | 173f55693ee7e391f22b398f45130a9403b2aba2 (diff) | |
| download | bcm5719-llvm-9bd5a4661cdfd11ae37dadc8758d27e4d9fd903c.tar.gz bcm5719-llvm-9bd5a4661cdfd11ae37dadc8758d27e4d9fd903c.zip | |
[gn build] Add check-lld target and make it work
Also add a build file for llvm-lit, which in turn needs llvm/tools/llvm-config.
With this, check-lld runs and passes all of lld's lit tests. It doesn't run any
of its unit tests yet.
Running just ninja -C out/gn will build all prerequisites needed to run tests,
but it won't run the tests (so that the build becomes clean after one build).
Running ninja -C out/gn check-lld will build prerequisites if needed and run
the tests. The check-lld target never becomes clean and runs tests every time.
llvm-config's build file is a bit gnarly: Everything not needed to run tests is
basically stubbed out. Also, to generate LibraryDependencies.inc we shell out
to llvm-build at build-time. It would be much nicer to get the library
dependencies by using the dependency data the GN build contains
(http://llvm-cs.pcc.me.uk/gen/tools/llvm-config/LibraryDependencies.inc#1).
Differential Revision: https://reviews.llvm.org/D55836
llvm-svn: 349702
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/expr-doesnt-deadlock')
0 files changed, 0 insertions, 0 deletions
