cargdev/angular
1
0
Fork 0
Code Issues 16 Pull Requests Actions Packages Projects Releases Wiki Activity

build: migrate references and scripts that set to build with ivy via compile=aot to use config=ivy (#33983)

Browse Source 
Since config=ivy now sets the define=compile flag and the define=angular_ivy_enabled
flag to cause usage of Ivy, we can update all of the documentation and scripts that
reference compile=aot to use config=ivy.

PR Close #33983
This commit is contained in:
Joey Perrott
2019-11-22 12:07:29 -08:00
committed by Matias Niemelä
parent d2784c7894
commit fec9f7dce5
10 changed files with 29 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
packages/core/test/render3/perf/README.md
View File

@ -1,7 +1,7 @@
### Build
```
yarn bazel build //packages/core/test/render3/perf:${BENCHMARK}.min_debug.es2015.js --define=compile=aot
yarn bazel build //packages/core/test/render3/perf:${BENCHMARK}.min_debug.es2015.js --config=ivy
```
### Run
@ -72,9 +72,9 @@ The resulting output should look something like this:
### Notes
To run the benchmark use `bazel run <benchmark_target>`, example:
- `yarn bazel run --define=compile=aot //packages/core/test/render3/perf:noop_change_detection`
- `yarn bazel run --config=ivy //packages/core/test/render3/perf:noop_change_detection`
To profile, append `_profile` to the target name and attach a debugger via chrome://inspect, example:
- `yarn bazel run --define=compile=aot //packages/core/test/render3/perf:noop_change_detection_profile`
- `yarn bazel run --config=ivy //packages/core/test/render3/perf:noop_change_detection_profile`
To interactively edit/rerun benchmarks use `ibazel` instead of `bazel`.