| commit | b026e2aab85cffe5ec3b77ea9c0d3a606373c28b | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Feb 27 14:09:25 2025 -0800 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Feb 27 14:09:25 2025 -0800 |
| tree | fb573853373cca01f9b3e1474b1f89ecf10a1ac6 | |
| parent | 00d1d18eb81dfd31b4cecc3dcae3cc4f8faadd97 [diff] |
roll: third_party/pigweed 9814a13..b4a0ee4 (8 commits) b4a0ee4:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271272 third_party/googletest: Add pw_third_party_googletest_ALIAS 2409b0e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271374 pw_allocator: Uniformly apply trait checks to block unit tests 569484f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271172 pw_kernel: Refactor scheduler to use ForeignBox/ForeignList ec058ef:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/270853 pw_kernel: Add ForeignList a16364a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/270752 pw_kernel: Add ForeignBox type 0ccc12d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/270832 pw_kernel: Move UnsafeList to deal exclusively with pointers 84eee29:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271373 pw_allocator: Reorganize block unit tests fdb976b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271153 pw_preprocessor: rm BUILD.bazel list comprehension Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 9814a13fd48140..b4a0ee4f9fff86 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8721744354281327057 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Iecf39c669bf86e7d547690af1207923a10fde03e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/271635 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>
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!
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
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
All of these commands must be run from inside an activated developer environment. See Environment setup
To build the project, documentation, and tests, run the following command in an activated environment:
pw build
Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:
pw watch
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
Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.