Explain how to handle device-specific headers.
Bug: N/A Test: N/A Change-Id: I12c41fcb4839ad86f5a1f62153a3348c3e40f90f
This commit is contained in:
parent
0d6485eca4
commit
a57c87827c
|
@ -171,6 +171,10 @@ As mentioned above, this is currently a two-step process:
|
||||||
contents for external/kernel-headers/.
|
contents for external/kernel-headers/.
|
||||||
2. Run update_all.py to scrub those headers and import them into bionic.
|
2. Run update_all.py to scrub those headers and import them into bionic.
|
||||||
|
|
||||||
|
Note that if you're actually just trying to expose device-specific headers to
|
||||||
|
build your device drivers, you shouldn't modify bionic. Instead use
|
||||||
|
`TARGET_DEVICE_KERNEL_HEADERS` and friends described in [config.mk](https://android.googlesource.com/platform/build/+/master/core/config.mk#186).
|
||||||
|
|
||||||
|
|
||||||
Updating tzdata
|
Updating tzdata
|
||||||
---------------
|
---------------
|
||||||
|
|
Loading…
Reference in New Issue