aver-updater: use unversioned libchrome libraray.
Libchrome is changing pkg-config and .so library name from
xxxx-${libbase_ver}.{pc,so} to xxx.{pc,so}.
Libchrome uprev rebuild will be handled by ebuild subslot change. And
there's no need to install multiple libchrome. Keeping libbase_ver
suffix will cause troubles on linking libraries when developers wants to
test locally emerge a-single-package without build_packages, after a
libchrome uprev. Especially in a case a package depends on another
package(library), and both depends on libchrome. Thus, removing
libbase_ver from suffix.
BUG=chromium:920513
TEST=CQ
Change-Id: If4eb8d8d7c43ba1d27ba356addca7a64a03c8aca
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/aver-updater/+/2505269
Reviewed-by: Joe Tessler <jrt@chromium.org>
Commit-Queue: Qijiang Fan <fqj@google.com>
Tested-by: Qijiang Fan <fqj@google.com>
diff --git a/src/module.mk b/src/module.mk
index 0f7bde0..80ec9f3 100644
--- a/src/module.mk
+++ b/src/module.mk
@@ -6,7 +6,7 @@
BINARY_NAME := aver-updater
-PC_DEPS = libbrillo libchrome-$(BASE_VER) libarchive
+PC_DEPS = libbrillo libchrome libarchive
PC_CFLAGS := $(shell $(PKG_CONFIG) --cflags $(PC_DEPS))
PC_LIBS := $(shell $(PKG_CONFIG) --libs $(PC_DEPS))
LDLIBS += $(PC_LIBS)