| Age | Commit message (Collapse) | Author |
|---|
|
Some targets do not create images for some non-system partitions, but
include them in the system partition. Even in such cases, create the
aconfig_flags in the etc directory of the original container.
For example, system_ext aconfig_flags.pb can be installed in
system/system_ext/etc/aconfig_flags.pb.
With this change, add system_ext to the aconfig paths along with the
other partitions.
Bug: 385213580
Test: lunch gsi_x86_64_soong_system-trunk_staging-userdebug && m
Change-Id: I660eb2e3d55850680ca610b8b756495d1769de4c
|
|
If RELEASE_FINGERPRINT_ACONFIG_PACKAGE is enabled, the storage file
version arg supplied to aconfig create-storage will be v2. Otherwise,
send v1 (current default).
As the build flag is not enabled, this change should be a no-op.
Confirmed by building that the files were still v1.
Test: manual
Change-Id: I2e3ef14c5a61bd1cbb2868f01a554af4d9e2a84b
|
|
Bug: 373685244
Test: m and inspect SYSTEM/etc/aconfig_flags.pb
Flag: EXEMPT flagging within flag infra
Ignore-AOSP-First: CPing aosp/3378710
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:5730ce71ac657ba88d2265148fa63ce1d10b105e)
Merged-In: I9a1d3d3589246b650326f8770209401ca388a734
Change-Id: I9a1d3d3589246b650326f8770209401ca388a734
|
|
Correct the comment for generate-partition-aconfig-flag-file to
describe the function.
Bug: na
Test: na
Change-Id: I8b4b35fa0a272a125ede4cf151ff72307247e0b5
|
|
Previously flag info file is created at run time rather than at build
time due to two reasons:
1, it saves some storage space on each container
2, initially the flag info file does not container any flag non run time
info, so creating this file at run time on device is more efficient.
However, flag info file is fairly compact, 1 byte per flag. So the
storage footprint increase is minimal. Also, now flag info file contains
flag information known at the build time such as if the flag is read
write. To help create flag info file at run time, we actually have to
keep additional information on flag map file. Then use this information
to create flag info file at run time. Now it is more efficient to just
create flag info file at build time.
In addition, to create flag info file at run time, we need to maintain
an additional write api create_flag_info_file. Each time flag file
version changes, we have to keep the old version of this API as well. If
we create flag info file at build time, then we don't have to maintain
this API.
Overall the benefits outweight the 1 byte per flag storage overhead.
Therefore making this change to create flag info file at build time.
Bug: b/301491148
Test: m
Change-Id: I33993a438bbaf8697214655288ced30817b9592e
|
|
Bug: b/365135457
Test: m
Change-Id: Iece264cdd49d84ef0e5acccdbcf68059c876395f
|
|
pertition
Test: m
Bug: 349410287
Change-Id: I6f706e90df7985e81865b18b353e4263dea72c0c
|
|
Flags should only be in one of the files.
Bug: 349410287
Test: manual, TH
Change-Id: I85376298538e2537f8f0f717a0a40a8545e99ea6
|
|
Move the make build rule for build_flags.json to soong.
Bug: 324996303
Test: m --no-skip-soong-tests
Change-Id: I958d5bb78db1d63b6145ac6a498490faa2fea315
|
|
Bug: b/328491388
Test: m
Change-Id: I278cfc9b8e1818d67514fbf1682850aa297ae851
|
|
Move them to under aconfig dir so it is easier to define SELinux policy.
Bug: b/312459182
Test: m
Change-Id: I2af7167a21e004729a9ac8628243080c893fb33a
|
|
Building device_aconfig_declarations creates simplifies listing all
aconfig flags used on the device by creating a build artifact at:
$(OUT_DIR)/target/product/$(TARGET_PRODUCT)/device_aconfig_declarations.pb
Bug: b/308625757
Test: manual
Change-Id: Ic5eef9c6a26f7893b3f4bdfed2cd4ac82a54a8f9
|
|
Bug: b/321243743
Test: tested in internal main build
Change-Id: I824c698587843fc72e8a16e8646262202663d99e
|
|
Add make file targets to create storage files. Note the container field
to aconfig command is an empty string for now as flags now by default
assumes empty container string in parsed_flag proto. Need to update it
once the container specification to aconfig files are done.
Bug: b/312239352
Test: m
Change-Id: If7bd12be5917a4779047633c00f88166574bfe0b
|
|
When Soong creates per-module aconfig files by merging aconfig files
from dependencies $(sort) is no longer sufficient to dedup identical
flags. Pass --dedup to aconfig dump.
Fixes: 313698230
Test: m out/target/product/vsoc_x86_64/system/etc/aconfig_flags.pb
Change-Id: Icd8a3fbff8fe0be1dbb617ac1db4bd73f35b2d2f
|
|
This reverts commit 49fbb31fcfe743fb80fa47db0d7909a9fb14edb8.
Reason for revert: textproto usages have been removed
Change-Id: I4021b5e79bcd114a610a529bc68e0be50500b339
|
|
This reverts commit 0ac530459825bc31a71acbd901575effbd88d681.
Reason for revert: unbreak FlagFlipper
Test: m
Change-Id: I3c00d97bcb39d50a54b46fb61eaa30e8fcb0c9a5
|
|
The /<partition>/etc/aconfig_flags.textproto files are no longer needed
(all clients have migrated to use /<partition>/etc/aconfig_flags.pb).
Stop generating them.
Also update how an empty file is generated in case there are no flags
for a given partition. Previously
echo "" > file
was used, which resulted in a file containing a newline, which caused
`printflags` to error out. Change the command to
echo -n > file
to create an empty file.
Bug: 302452801
Bug: 304278614
Test: m nothing
Change-Id: I2f7d23df4e888046651b4155b75c5006d0b5e1d7
|
|
Bug: 299907996
Test: manually confirmed that pb file is gen'd and cp'd to device
Change-Id: I8e5c7bb8b1ad234bd6f0dba4de1cbe3fe1df19ae
|
|
|
|
Bug: 293436986
Test: manual
Change-Id: I1d358faf9a0a3a83a92646c7cf7194c17ad2331e
|
|
Bug: 272358980
Test: build/soong/tests/sbom_test.sh
Change-Id: Ifcb2f26044c346c54e60d1d4fb85fc4001f64210
|
|
Bug: 283910439
Test: manual validation of outputs, soong unit tests
Change-Id: I5f7dc16ee42c3722dc66ffe964ed20479eea1e15
|