| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
filepath.Walk calls os.Lstat for every file or directory to retrieve os.FileInfo.
filepath.WalkDir avoids unnecessary system calls since it provides a fs.DirEntry,
which includes file type information without requiring a stat call.
This improves performance by reducing redundant system calls.
|
| |
|
|
|
|
| |
This unifies the build() and clean() interfaces such that if a custom
compiler or make binary is provided in the manager or bisection config,
they can be taken into account by the clean() interface.
|
| |
|
|
|
| |
Copy Cuttlefish module objects to be used
in coverage report generation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
More recent Android kernels may not use the DEFCONFIG_FRAGMENT and
BUILD_TARGET environment variables. Instead, they may require passing
additional flags the build script.
This allows specifying those additional flags and makes the
previously-required (and no longer used) configuration fields optional.
The older values can now be set via the new EnvVars field when needed.
We also need to look for the `autoconf.h` file in a different location.
This can now be configured using the `autoconf_path` configuration
field.
|
| |
|
|
|
| |
Copy unstripped module files in the output directory to be stored
in the object dir, to be used when generating module coverage.
|
| | |
|
| |
|
|
|
|
|
|
| |
Added config structure in build/Android to allow specifying
specific Android targets.
Build config is optional and extensible for individual build
instances.
|
| |
|
|
|
|
|
|
|
| |
Booting physical Android devices requires building a few artifacts, as described
at https://source.android.com/docs/setup/build/building-kernels.
When a ProxyVM type is used, we need to differentiate whether or not to
use the Android build logic, so we add an additional mapping which uses
a different name but the same VM logic.
|
| |
|
|
|
|
| |
Building images for physical Android devices has different logic and
options and should be in separate files. This makes it less ambiguous
and frees up android.go for Android device code.
|
| |
|
|
|
|
|
|
| |
Added functionality to build with bazel instead of 'build.sh',
as 'build.sh' is being depreciated.
Checks the branch information from 'build.config.constants' file
and uses Bazel for android14+.
|
| |
|
|
| |
The upstream kernel headers path was changed to the dist directory.
|
| |
|
|
|
|
| |
The directories the Android build scripts write to are controlled by
environment variables. This defines the OUT_DIR variable so that we can
get the .config file and copy it to the output directory.
|
| |
|
|
|
|
| |
Since the worker instances don't have network access, they won't be able
to download the Cuttlefish packages using this. Instead, we'll have to
pre-install the Cuttlefish tools in the GCE image.
|
| |
|
|
|
|
|
| |
Since it wasn't copied here, SyzCI would fail during image testing with
"failed to open ELF file: .../obj/vmlinux: ... no such file or
directory"
|
| |
|
|
|
|
| |
Add ability to trace build process and save debug artefacts.
Add tracing of ELF signature calculation.
Useful for debugging of #2297.
|
| |
|
|
|
| |
The command to fetch a Cuttlefish emulator binary is 'fetch_cvd', with
and underscore.
|
| |
|
|
|
|
| |
Since most of the image mounting code is duplicated, we can instead
extract it to an embedFiles() function that takes a callback. The Linux-
or Android-specific code can be in the callback.
|
|
|
Android uses some config files (specified with the BUILD_CONFIG
environment variable) to configure kernel builds. KASan configurations
already exist.
We want to mount the image, install a new Cuttlefish emulator binary
(using fetch_cvd) and copy over the kernel that we've built.
|
