commit 1cbf32569f32a4c3d581d5639440d9f8109ac87b
author Robert Kolchmeyer <rkolchmeyer@google.com> Fri Dec 03 12:12:04 2021 -0800
committer Robert Kolchmeyer <rkolchmeyer@google.com> Mon Dec 06 20:01:58 2021 +0000
tree f069da0d6ee1fc1bfe1cec9076c6d48819a9866c
parent 4f3d332f8e92c1969b7cd8b977b56d133bd3beac

cos-customizer: Refactor embeddings into main packages

Embeddings need to be compiled for the same platform as the executable
that they are embedded into. This is simpler to do when embeddings are
dependencies of binary targets instead of library targets.

One might say that this can be trivially accomplished with Bazel's
"--platforms" flag. This is not the case, because cos-customizer has two
parts; the part that runs in Cloud Build, and the part that runs on the
preload VM. The Cloud Build part must always be compiled for amd64,
while the preload VM part needs to be compiled for both amd64 and arm64.
The --platforms flag can't handle this kind of configuration. We will
take an alternative approach where binary targets will be duplicated
into amd64 and arm64 variants, and the final cos-customizer container
image will ultimately depend on both kinds of binary targets.

BUG=b/176990931
TEST=./run_tests

Change-Id: I5d92483503d834984bb7df5c78cb7c9590bd708c
Reviewed-on: https://cos-review.googlesource.com/c/cos/tools/+/25830
Cloud-Build: GCB Service account <228075978874@cloudbuild.gserviceaccount.com>
Reviewed-by: Roy Yang <royyang@google.com>
Tested-by: Robert Kolchmeyer <rkolchmeyer@google.com>