Age | Commit message (Collapse) | Author |
|
4080221 snap-temp-L23400000072087081
Change-Id: Ie62de95f3698a86d54e726416e44558633b80235
|
|
am: 559de4f511 am: 36b5f97520
am: 11449a22cb
Change-Id: I3e09c9c2106e1b87a12517a8fe707d377549b5de
|
|
am: 559de4f511
am: 36b5f97520
Change-Id: I3151fe559d2ccbf74d0ddadb14bb3a0263829613
|
|
am: 559de4f511
Change-Id: Idc57df59e44cd368d545404678f22e582ae6e061
|
|
am: f320c0cf71
Change-Id: I7eb6e0aaa932c44ed1502231e8698195efd1438e
|
|
4017105 snap-temp-L82600000064873863
Change-Id: I3dfbc6d346856d888dc8efc5d63002f63bbf0137
|
|
Bug: 38232827
Test: Build
Change-Id: I5a6d667a44522514d11af4cd821c1668e52f4777
|
|
3c4a94e84c am: a8916bf601
am: 47f0958c55
Change-Id: Iacb19893a4934846982b8bd8084c49a7fb7aa604
|
|
3c4a94e84c
am: a8916bf601
Change-Id: I0ddbd54362bb7022426f39f781d83d19e85ebdae
|
|
am: 3c4a94e84c
Change-Id: I9a7c01c806159b71ff1a37f11fc929df93035537
|
|
am: 394b004b77
Change-Id: I464914a8d90ed002740db83e3ef7f635fcfc6a96
|
|
Bug: 35314006
Test: Validated compilation on linux and mac host.
|
|
am: 6890627dcb
Change-Id: Id1215066d821c1f6c507d3327712adee6a1bc3aa
|
|
am: b46ee47ad8
Change-Id: Idd47b13245bc60fa99b54a0e3198935f83370a60
|
|
am: 7bdef41e6a
Change-Id: I415fafd27bdaf775b9260fb2ebdc288eca1ea73a
|
|
am: 23d9356cf8
Change-Id: Icf857f12fc17fe21b7ef87ef98d1ae304ca12f75
|
|
am: 7dee603070
Change-Id: Ie2422e069aa5c135fa9254b26e4ff913c19e5e60
|
|
am: c9027cbc05
Change-Id: I9335cac262d89653cce5ecb45a61fd5383618db8
|
|
By setting vendor_available, the following may become true:
* a prebuilt library from this release may be used at runtime by
in a later releasse (by vendor code compiled against this release).
so this library shouldn't depend on runtime state that may change
in the future.
* this library may be loaded twice into a single process (potentially
an old version and a newer version). The symbols will be isolated
using linker namespaces, but this may break assumptions about 1
library in 1 process (your singletons will run twice).
Background:
This means that these modules may be built and installed twice --
once for the system partition and once for the vendor partition. The
system version will build just like today, and will be used by the
framework components on /system. The vendor version will build
against a reduced set of exports and libraries -- similar to, but
separate from, the NDK. This means that all your dependencies must
also mark vendor_available.
At runtime, /system binaries will load libraries from /system/lib*,
while /vendor binaries will load libraries from /vendor/lib*. There
are some exceptions in both directions -- bionic(libc,etc) and liblog
are always loaded from /system. And SP-HALs (OpenGL, etc) may load
/vendor code into /system processes, but the dependencies of those
libraries will load from /vendor until it reaches a library that's
always on /system. In the SP-HAL case, if both framework and vendor
libraries depend on a library of the same name, both versions will be
loaded, but they will be isolated from each other.
It's possible to compile differently -- reducing your source files,
exporting different include directories, etc. For details see:
https://android-review.googlesource.com/368372
None of this is enabled unless the device opts into the system/vendor
split with BOARD_VNDK_VERSION := current.
Bug: 36426473
Bug: 36079834
Test: Android-aosp_arm.mk is the same before/after
Test: build.ninja is the same before/after
Test: build-aosp_arm.ninja is the same before/after
Test: attempt to compile with BOARD_VNDK_VERSION := current
Merged-In: I6cfc292fb4e2d903d8b2600a61fab74e330f8f54
Change-Id: I6cfc292fb4e2d903d8b2600a61fab74e330f8f54
|
|
By setting vendor_available, the following may become true:
* a prebuilt library from this release may be used at runtime by
in a later releasse (by vendor code compiled against this release).
so this library shouldn't depend on runtime state that may change
in the future.
* this library may be loaded twice into a single process (potentially
an old version and a newer version). The symbols will be isolated
using linker namespaces, but this may break assumptions about 1
library in 1 process (your singletons will run twice).
Background:
This means that these modules may be built and installed twice --
once for the system partition and once for the vendor partition. The
system version will build just like today, and will be used by the
framework components on /system. The vendor version will build
against a reduced set of exports and libraries -- similar to, but
separate from, the NDK. This means that all your dependencies must
also mark vendor_available.
At runtime, /system binaries will load libraries from /system/lib*,
while /vendor binaries will load libraries from /vendor/lib*. There
are some exceptions in both directions -- bionic(libc,etc) and liblog
are always loaded from /system. And SP-HALs (OpenGL, etc) may load
/vendor code into /system processes, but the dependencies of those
libraries will load from /vendor until it reaches a library that's
always on /system. In the SP-HAL case, if both framework and vendor
libraries depend on a library of the same name, both versions will be
loaded, but they will be isolated from each other.
It's possible to compile differently -- reducing your source files,
exporting different include directories, etc. For details see:
https://android-review.googlesource.com/368372
None of this is enabled unless the device opts into the system/vendor
split with BOARD_VNDK_VERSION := current.
Bug: 36426473
Bug: 36079834
Test: Android-aosp_arm.mk is the same before/after
Test: build.ninja is the same before/after
Test: build-aosp_arm.ninja is the same before/after
Test: attempt to compile with BOARD_VNDK_VERSION := current
Change-Id: I6cfc292fb4e2d903d8b2600a61fab74e330f8f54
|
|
262790d4eb am: c240507660
am: 00ed03a325
Change-Id: I5e4d9c86bddb3ab5ad33f912396828a16d1a660a
|
|
am: c240507660
Change-Id: I7195d40e03c86db000ecf0c9309ae8ba92bdab6a
|
|
am: 262790d4eb
Change-Id: I09767a8e4aafd74b70c9ed43ad89eece3f1ab5ff
|
|
This reverts commit beed40cf417bbfcaf3e884450d50dd38315a3318.
Change-Id: I949a70b2243af78da23acfb84e6fa348a6a6d70e
|
|
0b01841bef
am: 950f5a5b52
Change-Id: I7457613acaf12945f8a8a14c92f54fdf4f4f41de
|
|
am: 0b01841bef
Change-Id: I18b9cfe328c103c08f292aeb06c6bcdf72601622
|
|
am: beed40cf41
Change-Id: I5c4dccab3caa49247799f8d2a5bdd376f62ebbc7
|
|
am: 867af56881
Change-Id: I822a8b827e4aa91e3489cb3a50c55eacafffc9ff
|
|
am: 5ab0a1eff0
Change-Id: Ic3ac721c18beb978aad5ab2d28386270f93d6bcb
|
|
am: b6b1eb9428
Change-Id: I06aee5805189d50e2208770eda45cc5e8f5fc084
|
|
Bug: None
Test: Validated compilation
Change-Id: I62f2d9397a8e47b6bcc9d093198bde19fc0ca703
|
|
This appears to be a bug where a parameter is ignored in one of its
members.
BUG=None
Review-Url: https://chromiumcodereview.appspot.com/2414133005
Cr-Commit-Position: refs/heads/master@{#426617}
(cherry picked from commit 06bca199aa1931102f3f33c7911a45d46c799654)
Change-Id: If5454cd7b87a36673f19be13d73681adecc4ba54
|
|
bfef0a1364
am: ad9a0aa907
Change-Id: I94d521e0e6f46e2583bf01b76cb1ed28adda8961
|
|
am: bfef0a1364
Change-Id: I5bdaa9a13bf5d70f2baedc9f6dcf28af8f19b787
|
|
am: 4b1ad93f7b
Change-Id: Idaf955f1bfa6c2f646cf2c29c85ebb497dcdd086
|
|
* Tests which rely on being able to query for the end event in a pair
were not possible, partly because end events tend to be missing
information, and also because they did not reference their start
events
* Async event association can optionally be allowed for events which
span across process boundaries
BUG=None
Review-Url: https://codereview.chromium.org/2716023002
Cr-Commit-Position: refs/heads/master@{#455132}
(cherry picked from commit 83621ef58f633413145bd7093f16d56eb2c88103)
|
|
am: 419fefa997
Change-Id: I556c04c4502b6539d45b4ed8ac93d27316319178
|
|
am: 55a3fcc9db
Change-Id: I4272811997d27448cd2b2fd5c16b0c9520e60a93
|
|
am: 819d29e521
Change-Id: I9d858b59f17ae13ed69e96d6a2ef75b96a081a9f
|
|
Everything remaining in there is DBus stuff which should be removed.
Bug: 31602715
Test: mma
Change-Id: Id08ae22dc6e5adadd98481a04adf47781b24ce07
|
|
am: f0f2fea881
Change-Id: I3cc7d17dd2b973166f237ff9c254e37c5716c4c2
|
|
am: 458973e464
Change-Id: Ia03493c3878ef97779629d383a7aee78136068c8
|
|
am: 101b73f77a
Change-Id: I2c96b195c0337226a61789c679b92888dff321d3
|
|
Upstream files should be updated and approved upstream.
Bug: 33166666
Test: default build targets
Change-Id: Id9156f1001f3c28224b42f07fdad43dc48f6c042
|
|
Disable the experimental allocator shim on Android builds.
At this point we haven't identified a need for it and
prevents us from having to update the linker flags for
the many projects that have libchrome as a dependency.
Bug: 33239390
Test: Validated libchrome dependents (update_engine) can be built properly
without adding the -wrap* linker flags
Change-Id: I4e7e914883dfbc08b7eab9e0e175c14e59e386eb
|
|
am: 18d24cc7dd
Change-Id: I8c4253bdb366e111b06771f47e243a2664b98931
|
|
am: e9c86c53cd
Change-Id: Id5535c3487ef8ea9ff03eb512c505e811dd28829
|
|
am: eac11262ba
Change-Id: I199050179dad575a91118e18961e217b3e684bc3
|
|
am: 1c9187aa6d
Change-Id: Ib74e64f61e7bdae505552bfbb548f4c8f987b24c
|
|
See build/soong/README.md for more information.
libchrome-dbus stays in Android.mk for now due to the use of the
BRILLO_USE_DBUS conditional.
Test: mma -j
Test: out/host/linux-x86/nativetest/libchrome_test/libchrome_test
Change-Id: Icaffccd45f5a58f5a0d3f10784ca451048da07a1
|