Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 007557f07d3f5c1ed16c15ab49354067f32e007c
commit007557f07d3f5c1ed16c15ab49354067f32e007c[log] [tgz]
authorTed Pudlik <tpudlik@pigweed.infra.roller.google.com>Wed Jul 03 23:43:44 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jul 03 23:43:44 2024 +0000
tree521d2b129728f4c05ce7eb89aef76ac2b0b7c589
parentfe19647ae736a0fd0da44c17081bf786687d2cde [diff]
roll: pigweed, pw_toolchain: third_party/mbedtls: Rename build file

This will cause the file to be correctly syntax-highlighted by
CodeSearch, vim, and perhaps other tools.

To prevent breaking downstream projects, I copy the file for now, and
will remove the old file in a followup CL.

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

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