Google Git
Sign in
pigweed / pigweed / examples / 206557002f0ff484797a606b56c3690401d6c952
commit206557002f0ff484797a606b56c3690401d6c952[log] [tgz]
authorWyatt Hepler <hepler@pigweed.infra.roller.google.com>Mon Apr 28 12:13:19 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Apr 28 12:13:19 2025 -0700
tree83f2a58e859a59fa2372e6f4bdfb2b5fd42aa649
parentfec47c4da27cb84ff8c3639b7e2ff4b4198f9e7e [diff]
roll: third_party/pigweed pw_tokenizer: Nested Base64 detokenization updates

Update Base64 nested detokenization to handle more of the new format.
Support for base 10 and 16 tokens will be added in an upcoming change.

Also update pw::base64::IsValidChar() to return false for padding (=)
characters. This is more correct behavior and makes the function usable
with pw_tokenizer.

This commit has no effect on the Detokenize() function, only the
DetokenizeText() function. For DetokenizeText(),
//pw_tokenizer:detokenize_perf_test on a Cortex M4, shows

- No performance difference for passthrough text.
- The simplest message (DetokenizeText_NoArgs) is about 39% slower, but
  the difference is small in absolute terms.
- Longer / more complex messages range from 5% slower to 6% faster.

Original-Bug: b/339876876
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/282913
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Copybara-Verified: Copybara Service <copybara-worker-blackhole@google.com>
Original-Revision: 13e8d3fa2d0cd1e297da415b9831355ace3194be

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 80b243207eb931..13e8d3fa2d0cd1
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8716319595335139745
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I07698bef5b1405b675f0523f63824bb378df5cf1
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/286912
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 83f2a58e859a59fa2372e6f4bdfb2b5fd42aa649
  1. build_overrides/
  2. docs/
  3. examples/
  4. images/
  5. infra/
  6. libraries/
  7. targets/
  8. third_party/
  9. tools/
  10. .clang-format ⇨ third_party/pigweed/.clang-format
  11. activate.sh ⇨ bootstrap.sh
  12. .bazelignore
  13. .bazelrc
  14. .bazelversion
  15. .clang-tidy
  16. .gitattributes
  17. .gitignore
  18. .gitmodules
  19. .gn
  20. .pw_console.yaml
  21. activate.bat
  22. banner.txt
  23. bootstrap.bat
  24. bootstrap.sh
  25. BUILD.bazel
  26. BUILD.gn
  27. BUILDCONFIG.gn
  28. LICENSE
  29. MODULE.bazel
  30. navbar.md
  31. OWNERS
  32. pigweed.json
  33. pyproject.toml
  34. README.md
README.md

Pigweed Sample Project

This repository outlines the recommended way of using Pigweed in a new or existing project. Feel free to fork this repository, or read it as a reference.

For more information see the Pigweed Getting started guide.

Check back for more complex examples and features coming soon!

Getting started

Make sure you've set up Pigweed's prerequisites.

If you're on Windows, you can automate the initial setup by downloading the first-time setup script from cmd.exe:

curl https://pigweed.googlesource.com/pigweed/sample_project/+/main/tools/setup_windows_prerequisites.bat?format=TEXT > setup_pigweed_prerequisites.b64 && certutil -decode -f setup_pigweed_prerequisites.b64 setup_pigweed_prerequisites.bat && del setup_pigweed_prerequisites.b64

Then you can run the script with the following command in cmd.exe:

setup_pigweed_prerequisites.bat

Note: You may see a few UAC prompts as the script installs Git, Python, and enables developer mode.

Once that is done, you can clone this project with the following command:

git clone https://pigweed.googlesource.com/pigweed/sample_project

Environment setup

Pigweed uses a local development environment for most of its tools. This means tools are not installed to your machine, and are instead stored in a directory inside your project (Note: git ignores this directory). The tools are temporarily added to the PATH of the current shell session.

To make sure the latest tooling has been fetched and set up, run the bootstrap command for your operating system:

Windows

bootstrap.bat

Linux & Mac

source ./bootstrap.sh

After tooling updates, you might need to run bootstrap again to ensure the latest tools.

After the initial bootstrap, you can use use the activate scripts to configure the current shell for development without doing a full update.

Windows

activate.bat

Linux & Mac

source ./activate.sh

Building

All of these commands must be run from inside an activated developer environment. See Environment setup

One-shot build

To build the project, documentation, and tests, run the following command in an activated environment:

pw build

Automatically build on file save

Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:

pw watch

Typical workflow

When you pull latest repository changes, run bootstrap:

source ./bootstrap.sh

If you're just launching a new shell session, you can activate instead:

source ./activate.sh

and rebuild with:

pw build

More info and Examples

Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.