| commit | 05550bf97f84c10e09a8f872049a98ebf37f1e4a | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Mar 26 01:52:07 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 26 01:52:07 2024 +0000 |
| tree | f9cc86edd6f10354ff96b98ac7d9e6805fa6e2d1 | |
| parent | 18e2a8a1d5037ed756f6c467d24826f9eba73b8b [diff] |
[third_party/pigweed] Roll 8 commits 46d35e297c33fdc pw_hdlc: Fix sitenav a3591c5b35b18cd pw_toolchain: LLVM compiler-rt builtins 64ac90b74d9e8c7 docs: Generate doxygen html output locally 03aef93f460f15c pw_libc: Include strncpy fe3fd13e05aaec2 pw_bluetooth: Add emboss contributing section to d f55c3650f6b2cca pw_presubmit: Skip gn_teensy_build on mac-arm64 59c46d828848519 pw_channel: Set closed bit on FAILED_PRECONDITION 1a0707ec7f1aaf7 pw_channel: Respect sibling closure https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: ff2cbf8c82c8a69..46d35e297c33fdc Roller-URL: https://ci.chromium.org/b/8752445653630150385 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I6129c6961d7bc687d395e31ce91668e1ff06dbcd Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/199575 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.