platform_external_libevent/Android.bp, branch master

Mark libevent as recovery_available for update_engine_sideload

2018-10-23T20:46:40+00:00

Test: build update_engine_sideload
Change-Id: I6d2a5ca2a6bd121b9bae9d9d5690d545ab11d1ef

Use target.linux for all linux kernel based targets

2017-10-16T21:01:38+00:00

Now in Android.bp files, target.linux applies to all targets running a
linux kernel (android, linux_glibc, linux_bionic). So common
flags/sources/etc can be combined instead of copying them to each
target.

Test: m
Change-Id: I621d6be4c06a5ec5bc8c337fff28b5e7bae28927

Rename target.linux[_x86[_64]] to target.linux_glibc[_x86[_64]]

2017-10-02T17:41:08+00:00

In the future, target.linux will apply to all targets running a linux kernel
(android, linux_glibc, linux_bionic). So move all current users to the specific
linux_glibc.

There will be another cleanup pass later that will move some instances back to
target.linux if the properties should be shared with target.android and
target.linux_bionic, but target.linux needs to be removed first.

Test: out/soong/build.ninja identical before/after
Change-Id: I8216651b226e9b475dccb2497abf2dd6f9391bee
Exempt-From-Owner-Approval: build system cleanup

Remove default libraries

2017-09-28T23:21:34+00:00

libdl is part of system_shared_libs now. -ldl -lpthread -lm are now defaults
for host_ldlibs on Linux and Darwin. -lrt is a default for host_ldlibs on
Linux.

Test: m host
Change-Id: Ie73147c21d3fd49630b78edfcdff41d1dc03e49b
Exempt-From-Owner-Approval: build system cleanup

Merge "Revert "Revert "Upgrade to 2.1.8-stable (2017-01-22)." and "Probably Mac build fix?"""

2017-09-14T08:33:49+00:00

Revert "Revert "Upgrade to 2.1.8-stable (2017-01-22)." and "Probably Mac build fix?""

2017-09-13T13:18:03+00:00

This reverts commit 83a0c9c65a60a92d3ea5542596b3ba56db492c37.

Bug: 64543673
Test: make checkbuild
Test: Manual tombstoned test
Change-Id: I84bb128d1dec433195f2cbdbf70236ba17fa9955

Mark the module as VNDK or VNDK-SP in Android.bp

2017-09-07T08:29:52+00:00

As a VNDK/VNDK-SP module, Android.bp must have 'vndk' tag as well
as 'vendor_available: true'.

For a VNDK module, the 'vndk' tag has 'enabled: true'.
It will be installed system/lib(64)/vndk as a vendor variant.

For a VNDK-SP module, the 'vndk' tag has
'support_system_process: true' as well as 'enabled: true'.
It will be installed system/lib(64)/vndk-sp as a vendor variant.

Bug: 63866913
Test: build and boot with BOARD_VNDK_VERSION=current
Merged-In: I82e0d42be49ab578d8797d596e9915a60900bb47
Change-Id: I82e0d42be49ab578d8797d596e9915a60900bb47
(cherry picked from commit 9f3cfa4a068b94cead9271ae831d4b8bcf9abbbf)

Revert "Upgrade to 2.1.8-stable (2017-01-22)." and "Probably Mac build fix?"

2017-08-10T19:30:47+00:00

This reverts commits 2a572d125a91a4aafd3ad8ce87259fc640fa0763 and
af241a5c8c2cde0fab7d7d563276c1095b00e3b4, which break tombstoned.

Bug: http://b/64543673
Test: manual + treehugger

Upgrade to 2.1.8-stable (2017-01-22).

2017-08-07T23:58:18+00:00

Bug: N/A
Test: builds
Change-Id: Idbbdc1db3d01984a4f4b60f8fdf455140b6b7ca6

Mark as vendor_available

2017-04-11T04:26:45+00:00

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: I3aef3b8f6b7e5eba3e6036a460faf0ca6fc301d3