| commit | a7aa6fbb37e60a5cb4037bb503d28970b6fc8f4c | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Feb 13 14:54:37 2025 -0800 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Feb 13 14:54:37 2025 -0800 |
| tree | d6a29e15318ec1253759b2cc38c2d2e57a1eea2b | |
| parent | 8c79aa20c060be99004d36c12100b97dcc8c0993 [diff] |
roll: third_party/pigweed 057c218..e1d73a0 (8 commits) e1d73a0:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267812 pw_sync: Remove chrono dependency from borrow.h 5f8f25b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/264636 pw_allocator: Refactor size reports fb3288a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267033 pw_ide: Detect & configure build system support 4bfb4e5:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267514 pw_kernel: Add unittests for new list routines 8335a60:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267513 pw_kernel: Add assert_ne to unittests 9808716:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267336 pw_kernel: Basic context switch for cortex-m and scheduler a8a94ac:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/259657 pw_ide: Read legacy settings files 7cee22f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267792 pw_toolchain: Add linker options for the Cortex-A35 toolchain Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 057c2187d3731d..e1d73a02c47f07 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8723010154246143649 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Id799098d9822efcc85848d2a393ce7b231af72ba Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/267855 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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.