am a8fe453f: am ed3555f5: am 468f8410: Merge "Add documentation about checkbuild."
* commit 'a8fe453f76ba107566cc5d531e78eba0bbbc9351': Add documentation about checkbuild.
This commit is contained in:
commit
a16d941ebc
12
README.md
12
README.md
@ -174,6 +174,18 @@ This is fully automated:
|
|||||||
1. Run update-tzdata.py.
|
1. Run update-tzdata.py.
|
||||||
|
|
||||||
|
|
||||||
|
Verifying changes
|
||||||
|
-----------------
|
||||||
|
|
||||||
|
If you make a change that is likely to have a wide effect on the tree (such as a
|
||||||
|
libc header change), you should run `make checkbuild`. A regular `make` will
|
||||||
|
_not_ build the entire tree; just the minimum number of projects that are
|
||||||
|
required for the device. Tests, additional developer tools, and various other
|
||||||
|
modules will not be built. Note that `make checkbuild` will not be complete
|
||||||
|
either, as `make tests` covers a few additional modules, but generally speaking
|
||||||
|
`make checkbuild` is enough.
|
||||||
|
|
||||||
|
|
||||||
Running the tests
|
Running the tests
|
||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user