roll: third_party/pigweed 243485c..61c3616 (10 commits) 61c3616:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/297537 pw_sync_zephyr: Export files for zephyr build 54bb4b0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/297592 pw_kernel: Arches store kernel state singleton a52507d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/297512 pw_kernel: `ArchInterface` -> `KernelContext` c03230c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/297492 pw_kernel: Permit arch dep injection in scheduler 437a6b0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/297335 pw_kernel: Simplify thread and process initialization 02d8407:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/296952 pw_chrono_zephyr: Export files for zephyr build 3e6a8fb:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/297674 pw_string: Build and test the buffer example e665314:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/299414 pw_allocator: Remove unused ContiguousBlock::AsBytes() declaration acbe158:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/289638 pw_multibuf: Add MultiBuf v2 ee5db46:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/297072 pw_result: Add tests for `expected<void, E>` Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 243485c98e86c5..61c3616d25f742 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8711684103445601825 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I677b1a1679a8a034b057058ab9efc28a5d6af7db Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/299572 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 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.