roll: third_party/pigweed 889c3d6..88ff1ab (13 commits)

88ff1ab:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309440 pw_ide: Remove "refresh compile commands and set target" command entry
a647434:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309477 pw_ide: Use VS Code's when clause to manage command availability
87f7abc:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/308413 pw_build: Update rust edition to 2024
e2552c5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/307876 pw_sync: Adjust unit test namespacing
a2d2850:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/299832 pw_trace_tokenized: Decouple buffer clearing from trace stop
d802b1a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/306952 pw_trace_tokenized: Fix incorrect timestamp
93d7208:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/303112 pw_trace_tokenized: Use pw_sync for trace locking
94612e0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/298892 pw_trace_tokenized: Get platform clock parameter
6661c8a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309443 Revert "pw_log_fuchsia: Update to new Fuchsia logging API"
67a7bac:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309438 pw_presubmit: Support formatting Go in Bazel projects
963ed52:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309437 pw_presubmit: Enable Starlark formatting
40e21b5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309475 pw_ide: Fix clang path on fish shell
b341c2f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309478 pw_ide: Enable composite tsconfig for VSCode dev

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 889c3d6ebdde8e..88ff1ab327ba3f
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8707898083890712833
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Idacbb10ae30b38751106bb158d3211e4133dd937
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/309793
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: 3c11ce9a16ba6ad8d0202905e05acb954614107f
  1. build_overrides/
  2. docs/
  3. examples/
  4. images/
  5. infra/
  6. libraries/
  7. targets/
  8. third_party/
  9. tools/
  10. .bazelignore
  11. .bazelrc
  12. .bazelversion
  13. .clang-tidy
  14. .gitattributes
  15. .gitignore
  16. .gitmodules
  17. .gn
  18. .pw_console.yaml
  19. activate.bat
  20. banner.txt
  21. bootstrap.bat
  22. bootstrap.sh
  23. BUILD.bazel
  24. BUILD.gn
  25. BUILDCONFIG.gn
  26. LICENSE
  27. MODULE.bazel
  28. navbar.md
  29. OWNERS
  30. pigweed.json
  31. pyproject.toml
  32. 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.