| commit | 323a8561b4252fb743fc94eeca15c031ad52152d | [log] [tgz] |
|---|---|---|
| author | Saswat Padhi <spadhi@chromium.org> | Mon Jan 27 13:54:07 2025 -0800 |
| committer | Saswat Padhi <spadhi@chromium.org> | Mon Jan 27 13:57:02 2025 -0800 |
| tree | cab95663353cd20bb70ae93b939c25613ce55c7f | |
| parent | 89f20a687e25ede6370070c29ada17ab29a68c99 [diff] |
build/debian: Fix the resolution of build script's directory The `$(dirname "$0")` pattern used throughout build.sh does not reliably point to the build script's directory. The linked bug report highlights an issue where `$(dirname "$0")` captures a relative path that is invalidated after changing the current working directory. We fix this by capturing the absolute path to the build script's directory at the beginning of the build script, and using it in place of the existing `$(dirname "$0")` calls. We also fix the build.sh invocation within build_in_container.sh to mimic our Kokoro build scripts. Bug: 392644919 Change-Id: Ia1623a16e9869a30e374577bd76802d2339f1b7b Test: ./build_in_container.sh -k Test: ./build_in_container.sh -k -a aarch64
Android Virtualization Framework (AVF) provides secure and private execution environments for executing code. AVF is ideal for security-oriented use cases that require stronger isolation assurances over those offered by Android’s app sandbox.
Visit our public doc site to learn more about what AVF is, what it is for, and how it is structured. This repository contains source code for userspace components of AVF.
If you want a quick start, see the getting started guideline and follow the steps there.
For in-depth explanations about individual topics and components, visit the following links.
AVF components:
AVF APIs:
How-Tos: