roll: third_party/pigweed pw_async: Make re-posting not an error Previously, re-posting a task was an error that would result in a crash. In practice, reposting tasks is common and the previous strict behaviour wasn't catching bugs. Thus, switch the semantics to allow reposting a task. New semantics: Post() - if task already posted and runnable: do nothing, retaining queue position. - if task already posted and scheduled: switch to run-immediately but at the end of the queue. PostAt() - always re-post to the new time Original-Bug: b/309465648 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/347412 Original-Revision: 5c5248374dec90577a58e5b0ff97d094f6c41c1c Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 11987af0771a4f..5c5248374dec90 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8678037362719160417 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I8d0bf9fe64888329788369c6f5941203100454ac Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/429112
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/examples/+/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/examples
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.