commit ed8280dbc64c8d15b4ab07355717e62ad7e7d7c3
author Renato Mangini Dias <mangini@google.com> Fri Dec 02 00:57:29 2022 +0000
committer Renato Mangini Dias <mangini@google.com> Fri Dec 02 00:57:29 2022 +0000
tree 07f00749b2a6de1cb239143afcc35b6bca578f28
parent b5fe47c0bf66d60f861cb6ea18c432ffbef2e723

Add platform selection to .bazelrc based on --config

In recent CLs, if_fuchsia was changed to rely on the platform
definition, which works fine if the target has a platform transition like
fuchsia_package or fuchsia_cc_binary, or if the user explicitly
specifies `--platforms=@rules_fuchsia//fuchsia/constraints/platforms:fuchsia_x64`

However, we have not fully migrated to platforms, and specifying the
crosstool_top and cpu is still required. So, in order to build a target
that does not go through a forced transition, the user would need to
specify both `--config=fuchsia_*` and `--platforms=...`, which is very
verbose.

This CL adds the appropriate `--platforms=` to .bazelrc, so
`--config=fuchsia_x64` sets both cpu, crosstool and platforms.

It is not ideal though because AFAICT it makes it impossible to build
for the host while using these --config options, unless if the target
has a platform transition. But since our focus on the sdk-samples for
now is to build for the Fuchsia target, I believe this should be ok
until we fully transition to platform and remove the requirement of
using cpu and crosstool.

Fixed: 116517

Change-Id: I1fbc255887a57bcaa4719aa7e6785c549991d57e
Reviewed-on: https://fuchsia-review.googlesource.com/c/sdk-samples/getting-started/+/769587
Reviewed-by: Chase Latta <chaselatta@google.com>
Reviewed-by: Wayne Piekarski <waynepie@google.com>
Reviewed-by: Renato Mangini Dias <mangini@google.com>