dd46ad41ff
This splits the existing full.mk in two parts: -One is the device-independent full_base.mk -The other is the emulator-specific device.mk This way we'll be able to inherit from full_base.mk for on-device builds without any emulator-specific files getting in the way. Change-Id: Ieb1f4ed47988c8fff119ff53f1f374032da3752d |
||
|---|---|---|
| .. | ||
| AndroidBoard.mk | ||
| BoardConfig.mk | ||
| device.mk | ||
| README.txt | ||
| system.prop | ||
| tuttle2.kcm | ||
| tuttle2.kl | ||
The "generic" product defines a non-hardware-specific target without a kernel or bootloader. It can be used to build the entire user-level system, and will work with the emulator, though sound will not work (see the "emulator" product for that). It is not a product "base class"; no other products inherit from it or use it in any way.