[roll third_party/pigweed] pw_toolchain_bazel: Apply more common attrs to cc_toolchain targets

Forwards tags, compatible_with, target_compatible_with, and
exec_compatible_with to the rules stamped out in cc_toolchain rules to
allow exclusion of these rules from wildcard builds.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/194890

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: f62f5f97e34fc05..8ea97acdb603f7b
Roller-URL: https://ci.chromium.org/b/8754331492520967585
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I838e0419d32dd908f294921129290fcc1a83028c
Reviewed-on: https://pigweed-review.googlesource.com/c/example/echo/+/194882
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: b1373d15fb8b52514daa076be6f383b241d077db
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. README.md
  12. requirements.in
  13. requirements_lock.txt
  14. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

git clone --recursive https://pigweed.googlesource.com/example/echo

If you already cloned but forgot to include --recursive, run git submodule update --init to pull all submodules.

TODO: b/300695111 - Don't require submodules for this example.

Building

We‘ll assume you already have Bazel on your system. If you don’t, the recommended way to get it is through Bazelisk.

To build the entire project (including building the application for both the host and the STM32 Discovery Board), run

bazel build //...

To run the application locally on your machine, run,

bazel run //src:echo

Flashing

To flash the firmware to a STM32F429 Discovery Board connected to your machine, run,

bazel run //tools:flash

Note that you don't need to build the firmware first: Bazel knows that the firmware images are needed to flash the board, and will build them for you. And if you edit the source of the firmware or any of its dependencies, it will get rebuilt when you flash.

Communicating

Run,

bazel run //tools:miniterm -- /dev/ttyACM0 --filter=debug

to communicate with the board. When you transmit a character, you should get the same character back!