| commit | 7e89c45785e2abe96a2f26dc9f510b688b6b94f2 | [log] [tgz] |
|---|---|---|
| author | Chad Norvell <chadnorvell@pigweed.infra.roller.google.com> | Wed Jun 26 17:25:31 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 26 17:25:31 2024 +0000 |
| tree | 7ee6d35b8737d3e5b28c0fa5ad57ace2b2e08730 | |
| parent | 0822cb12b33f5ef2221926c7e82a0fc5e86b7c08 [diff] |
roll: pigweed, pw_toolchain: pw_ide: Add option to process comp DBs by path As an alternative to the current method of searching for compilation databases in your source and build tree, this adds an option to directly specify the path(s). This is particularly helpful for Bazel- based projects for two reasons: 1. The predominant approach to generating compile commands in Bazel world is to just generate a single file with all commands in the root dir of the project, so there's no need to search for files. 2. By default, tooling runs within the Bazel environment, which could be located somewhere completely different from project checkout dir. So the search-based approach's assumptions of known source and build dirs breaks down. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218334 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 51ed6ec5209e23c..64f458827b65993 Roller-URL: https://ci.chromium.org/b/8744048389785160017 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I2a9fe22d62e072a7475c74884465aa8029799197 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218491 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
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.
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
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.
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!