From e66d57f532ba0ac2be8c70527b483b4a1c35e5f4 Mon Sep 17 00:00:00 2001 From: Dan Albert Date: Wed, 12 Nov 2014 17:08:38 -0800 Subject: [PATCH] Add documentation about checkbuild. Change-Id: I2c2d06bc0dc3cdc58b5563f62889122b76f3c469 --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index 300b98ff1..a031fbc14 100644 --- a/README.md +++ b/README.md @@ -174,6 +174,18 @@ This is fully automated: 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 -----------------