Previously if a library has custom generated headers in
LOCAL_GENERATED_SOURCES and export its include path with
LOCAL_EXPORT_C_INCLUDE_DIRS, there is almost no way for the users of the
library to set up dependency of their object files on the generated
headers.
This change makes the generated sources dependency of the library's
export_includes, which is guaranteed generated before client code gets
compiled.
Also we added proto-generated cpp files to my_generated_sources so that
we can deal solely with $(my_generated_sources). Because many
Android.mks assume the generted .pb.hs are in $(generated_sources_dir)
instead of $(intermediates), we have to generate the source files in
$(generated_sources_dir) and make a copy in $(intermediates).
Bug: 28622149
Change-Id: I73b21443fa706f3735faf16356ed8c08fbfecca6
am: 374c7facd5
* commit '374c7facd565b4d896db20ee04c94e90dee4c8e7':
Only pass NINJA_ARGS to the main ninja compile
Change-Id: I98f588bf7d9c39bf2a9ac7c07bfb15f19299694d
This way commands like "-t query <target>" will work against the main
build, instead of failing to find the target during the initial soong
build and stopping.
Change-Id: I9b6bd6ac431b95e12db69ec7f272669b9d292761
When invoking clang for the host to assemble .S files, the -B flag
would not be provided, which allowed the host prebuilt clang to
use an 'as' from the native environment. Most of the time this
"just works", but some newer 'as' versions cause problems with
the older prebuilt toolchain, for example by generating
unsupported relocation types.
To avoid this problem, simply use the -B flag to tell clang to
invoke the assembler from the correct prebuilt gcc prefix.
Change-Id: I18ea4f37ae637b652cfd7321c41929f8be075342
Signed-off-by: Alistair Strachan <alistair.strachan@imgtec.com>
am: b60b340597
* commit 'b60b340597ab4d1058b2a676e619531d2c829e40':
JAR signing logic for the apksigner-core library.
Change-Id: Ie90f89c7276839bda3e5e3246807d6cd18397d74
am: 33d34ae236
* commit '33d34ae236e487b04696d913d2b327d4c3b8c251':
SHA-256 with ECDSA supported only on API Level 21 and higher.
Change-Id: I0253d5ff12e735ba3ed0900ef8577662253de17b
apksigner-code library will offer a high-level primitive (future
commit) for signing APKs. This is meant to be used by
build/tools/signapk and Android Studio's APK builder/signer.
This commit adds a lower-level JAR signing (aka v1 signing) code which
will be used by the future APK signing abstraction exposed by this
library.
All classes added by this commit are internal (i.e., implementation
details of this library). Clients of this library should not be using
these classes.
Bug: 26516150
Change-Id: I5cecd435e63aab206d63868be5e0d0e289e7c423
Turns out APK signatures using SHA-256 with ECDSA are accepted only by
platforms with API Level 21 and higher, not 18 and higher.
Bug: 28296599
Change-Id: I3fab5be17bf3a9bdbf4d84d90d51448027c7e761
am: cc3440cc1d
* commit 'cc3440cc1d101c225cbe2a42fe4046d3a44b3927':
Separate logic for alg selection for OTA and APK signing.
Change-Id: Iaed58ff5398ac0637129b3f45eb3a1226e891226
am: 11821a1e1e
* commit '11821a1e1e1360ceb1ad83f55715d7415c385633':
old-cts: Add testng and libcoreoj test support
Change-Id: I0f838aebab9aea750217e9351e03f19410ba049c
am: a6da20e2d2
* commit 'a6da20e2d29b3bbde0b1b9101727cd6ea8b9c9c4':
Initialize an uninitialized field in ijar
Change-Id: Iee38d8d3eb2ff20d8e4d1cf876e83bfdac5e3391
This updates the usage banner of zipalign to state that the -p switch
is supported in check alignment mode.
Change-Id: I119026b0e09e5a2528646e88a9b58dbb79c0c17c
am: 85b9117
* commit '85b911719084b7266de459408e8f038a2a429e0c':
Warn if there is file with unknown suffix in Java module's sources.
Change-Id: I6c7d7a6b51f63f9b6f0da8b6e35d73d46820cae4
Ying Wang