Commit Graph

2 Commits

Author SHA1 Message Date
Chris Masone
6224cba9c7 [crosutils] Make chromium/libcros mismatch messages more semantically accurate
The messages printed out by the code that checks if chromium's libcros and the system's libcros are
in sync were kind of confusing and not quite accurate.  The system library implements a range of API
versions, and it is chromium that requires a particular version of the API.  The messages now clearly
reflect this.

BUG=None
TEST=manual

Change-Id: I7308d7eb724edfb7fa11edbe0fbec86ee12c5afe
Reviewed-on: http://gerrit.chromium.org/gerrit/1136
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
2011-05-19 13:31:52 -07:00
David James
f86703dd5d Move libcros check from chromeos-chrome into test_build_root.
This is needed for eliminating the dependency between chromeos-chrome and libcros.
This also has the benefit that builds will fail if you take a binary version of
chromeos-chrome with an incompatible version of libcros.

BUG=chromium-os:15145, chromium-os:15148
TEST=build_packages --nousepkg && build_image.
     Test that test_image fails when libcros version is wrong.

Change-Id: I46cbc4494d36b13ba1bdda699eccb6dc7fea162c
Reviewed-on: http://gerrit.chromium.org/gerrit/633
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
2011-05-10 15:05:12 -07:00