Google Git
Sign in
pigweed/pigweed/quickstart/bazel/5b97bc7cedc5ab16dfa8ffdbbbaf9b6d833937e4
commit
5b97bc7cedc5ab16dfa8ffdbbbaf9b6d833937e4
[log]
author
Jiacheng Lu <lujc@pigweed.infra.roller.google.com>
Thu Aug 01 06:23:45 2024 +0000
committer
CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Thu Aug 01 06:23:45 2024 +0000
tree
1133f7d0317bc91e27359aeea57e89730e16a18f
parent
25f8042cdf008ad055880f268753ee8af69247e2 [diff]
roll: pigweed, pw_toolchain: pw_toolchain: proc_macro GN cross compile

proc_macro is always compiled using host toolchain. Switch to the
host toolchain for cross compiled proc_macro targets.
The `pw_toolchain_SCOPE` variable is used to access toolchain type nad
name for the switching. Move its definition to a separate gni file to
avoid circular importing.

Test: Manually verified host and target hello executable
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/215011
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: ddcc251bcac0c2c..e194c83f1d06383
Roller-URL: https://ci.chromium.org/b/8740828568382194753
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I4e0c888cd1075fe63650e3fa9bce0319e19e5d52
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226860
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 1133f7d0317bc91e27359aeea57e89730e16a18f
  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!