path: root/Android.bp
AgeCommit message (Collapse)AuthorFilesLines
2017-07-25Mark the module as VNDK or VNDK-SP in Android.bpaosp-new/oreo-mr1-devJustin Yun1-0/+3
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 Change-Id: I50f7d1df4ed1ea1928d0881495e28ae4f379acf5
2017-04-13libnl: mark as vendor_availableandroid-wear-o-preview-4android-wear-o-preview-3android-wear-8.0.0_r2android-wear-8.0.0_r1android-vts-8.0_r2android-vts-8.0_r1aosp-new/oreo-devSteven Moreland1-0/+1
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: None of this is enabled unless the device opts into the system/vendor split with BOARD_VNDK_VERSION := current. Bug: 36426473 Bug: 36079834 Test: m -j libnl Test: attempt to compile with BOARD_VNDK_VERSION := current Change-Id: I84c5f871cba9c0e67350e04f5e9f34489470f34e
2017-04-13libnl: -> Android.bpSteven Moreland1-0/+50
Converting to be able to use some Soong features not available in make. Test: (sanity) build and flash marlin device, works Bug: 33241851 Change-Id: If1f3f5fd5f6b1999011c25ac8b8107f12648435b