summaryrefslogtreecommitdiff
path: root/power/mediatek.c
diff options
context:
space:
mode:
authorVadim Bendebury <vbendeb@chromium.org>2015-11-02 14:24:50 -0800
committerchrome-bot <chrome-bot@chromium.org>2015-11-04 07:08:45 -0800
commitd5e49bc23da47bca149b85682c01ef61a69e7bb8 (patch)
treec86df00977627dbbacbdb0a8eb6ec9bd893eb7fe /power/mediatek.c
parenta25c7025e11a9abc0fea873de73148770105fcb3 (diff)
downloadchrome-ec-d5e49bc23da47bca149b85682c01ef61a69e7bb8.tar.gz
make: decouple rw and ro object file sets
When building EC image, in the majority of cases the RW and RO images are built from exactly the same set of object files, and the RO set of objects is used as a template to derive the RW set of objects. This is not necessarily correct in all cases, let's just create an abstract set of object files and use it to derive the sets for RO, RW and sharedlib as appropriate. BRANCH=None BUG=chrome-os-partner:43025 TEST=tested as follows: - changed the Makefile to sort all object files in a single list (instead of sorting them by directory, with the directory list unchanged). Built all targets, saved all .smap files. Then applied this change and again built all targets. Compare all smap files, there were no differences. - modified board/samus/board.h to trigger building sharedlib objects, verified that build/samus/sharedlib built fine. Change-Id: Ie563aca62028cae9e16f067ba20b5e2930355cf5 Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/310389 Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
Diffstat (limited to 'power/mediatek.c')
0 files changed, 0 insertions, 0 deletions