免费咨询医生回答在线妇科_web浏览器有哪些软件_做网站推广_软文通

Android VNDK

Build system help to check depedencies between modules, build a vendor-specific variant for vendor modules and automatically installs these modules into designed directories.

When the dependencies are invisible to the build system (e.g. shared libraries that may be opened with dlopen() in runtime), you should specify the module names in PRODUCT_PACKAGES to install those modules explicitly.

The Vendor Native Development Kit (VNDK) is a set of libraries used by other libraries or binaries, in the vendor or product partition, on runtime for dlopen.
These libraries are used by the vendor image, on the system image.

cc_library {
name: “libThatIsCore”, 
… 
}

cc_library { 
 name: “libThatIsVendorOnly”  
 proprietary: true, 
 # or: vendor: true, # (for things in AOSP) 
 … 
}

cc_library { 
 name: “libThatIsVendorAvailable”, 
  vendor_available: true, 
 … 
}

cc_library { 
 name: “libThatIsVendorAvailable”, 
 vendor_available: true, 
 vndk: { 
  enabled: true, 
 } 
… 
}

cc_library { 
 name: “libThatIsVndkSp”, 
 vendor_available: true,
 vndk: { 
  enabled: true, 
  support_system_process: true,
 } 
… 
}

cc_library {
 name: “libThatIsLlndk”, 
 llndk: { 
  symbol_file: “libthatisllndk.map.txt” 
 } 
 … 
}

参考资料：

• https://source.android.com/docs/core/architecture/vndk/enabling
• https://source.android.com/docs/core/architecture/vndk