roll: pigweed, pw_toolchain: bazel: Roll out incompatible_with_mcu

This change was automatically generated by running the following script:

    #!/bin/bash
    STRING="target_compatible_with = select(TARGET_COMPATIBLE_WITH_HOST_SELECT),"
    REPLACEMENT="target_compatible_with = incompatible_with_mcu(),"

    for p in `git grep -l "$STRING"`; do
      echo "Replacing in $p"
      sed -i "s/$STRING/$REPLACEMENT/g" $p
    done

    # Add loads of incompatible_with_mcu to every package, and then remove them if
    # anywhere they're unused..
    /usr/bin/buildozer 'new_load //pw_build:compatibility.bzl incompatible_with_mcu' //...:__pkg__
    /usr/bin/buildozer 'fix unusedLoads' //...:__pkg__

Original-Bug: 348008794
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216852
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: c703cce68d0d061..bfaf596d3e1231c
Roller-URL: https://ci.chromium.org/b/8743503387820103521
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I0cd85b33944c58ffaa3b988d90a576add9463d6f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/219652
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 6b13cd1978990865636497768e4370d271b405fd
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  13. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. 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/pigweed/quickstart/bazel

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!