| commit | 1de5e4fdd322eea947d1675f38a8b27bf37e8a3c | [log] [tgz] |
|---|---|---|
| author | Rich Kadel <richkadel@fuchsia.infra.roller.google.com> | Fri Mar 04 23:28:28 2022 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 04 15:29:46 2022 -0800 |
| tree | a16ea5760ceca4226a1ebded59598c248fcdb167 | |
| parent | f6ab990351948d6048d1f23cdcd6aede415b0cad [diff] |
[roll] Roll fuchsia [build][dart] Default to AOT in release mode, and corrected GN template errors
The root cause behind the following bug is resolved, so the build
scripts should no longer force JIT for release builds.
Original-Fixed: 64126
Also...
`dart_test_component()` and `flutter_test_component()` accept a
`build_cfg` variable from the invoker, but the GN syntax was wrong.
Builds failed when I tried to use it to force an individual test to run
in AOT mode (by supplying the dart_aot_runner in the test's
configuration).
Note, this is what I added to my `dart_test_component()` declaration,
which works, with the changes in this CL:
```gn
# Fuchsia non-system tests do not have permissions for
# `ambient_mark_vmo_exec` (per the current `component_manager_policy`),
# which is required by the JIT runners, so build the test in AOT
# mode, only, and serve the AOT runner from the test component's
# environment.
if (is_debug && !dart_force_aot) {
# Note that `dart_aot_debug_build_cfg` does not work in the default,
# non-release Fuchsia build because that config enables asserts, and
# the current AOT VM apparently requires `no-asserts`.
build_cfg = dart_profile_build_cfg
}
```
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/653646
Original-Revision: 8fc0dcf8b9692093826b4e867f87930459f78478
GitOrigin-RevId: 049cab0b6af7cd9ae975a89db60e60e406f3dfa5
Change-Id: I4a22694f8a776efd8ce3dbf608a99b77b220b5fb
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.