[roll third_party/pigweed] pw_allocator: Fix #if PW_HAVE_FEATURE(__cpp_rtti)

Since __cpp_rtti is a standard feature test macro, it should not use
__has_feature.

Additionally, this CL takes the opportunity to reduce the number of preprocessor directives added by CL 210571.

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

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 83644e88fe7aa51..5e6b6c962de2402
Roller-URL: https://ci.chromium.org/b/8747234864982914609
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I16e1972071b2e25684b0612ff29d18ce2b3089f6
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210971
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 0057b51453d2615636423c2811e45d0f7b07b6b4
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!