commit | bf23395b8d5c67ed5dccf457db61a84616279c84 | [log] [tgz] |
---|---|---|
author | Derek Schuff <dschuff@chromium.org> | Tue Apr 03 22:25:38 2018 |
committer | GitHub <noreply@github.com> | Tue Apr 03 22:25:38 2018 |
tree | 7b5086d94d86a49ecfe82e4f2d363b82f180d7b7 | |
parent | a787fdd21e18eb7e044796832472e4137b3437a1 [diff] |
Update libcxx/abi builds (#349) * Remove forcing of COMPILER_WORKS in favor of using -nostdlib++ * Use LLVM_PATH instead of LLVM_CONFIG_PATH because the latter doesn't work on windows (something about paths)
Luckily, this repository has some tests:
This repository holds the code which make the WebAssembly waterfall‘s heart beat. You may want to see the waterfall in action, and if you don’t like what you see you may even want to contribute.
WebAssembly has many moving parts (implementations, tools, tests, etc) and no central owner. All of these parts have have their own owners, priorities, and tests (which include WebAssembly as well as others). A build and test waterfall allows us to test the interactions between these components. It helps us:
We should keep process to a minimum, try things out, see what works.
$ git clone https://github.com/WebAssembly/waterfall.git
python src/build.py
Build.py has 3 types of actions:
$ src/build.py --no-sync --build-exclude=llvm
$ src/build.py --sync-include=wabt --build-include=wabt,binaryen --test-exclude=emtest,emtest-asm
The script should throw an error if you specify nonexistent steps or if you specify both includes and excludes for the same type of action.
When run, the script creates a directory src/work
inside the waterfall‘s git checkout. All modifications are made inside this directory (checking and out and building the sources, as well as the test builds and execution results). You can also use the git checkouts (e.g. src/work/llvm
) with your own branches; the sync steps will check out the latest revision from the script’s remote repositories but will not overwrite or destroy any local work.