| commit | 3ba89c43edd85e5493ac5d7668da9942ecfe150c | [log] [tgz] |
|---|---|---|
| author | Carlos Chinchilla <cachinchilla@pigweed.infra.roller.google.com> | Fri Feb 16 03:27:39 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 16 03:27:39 2024 +0000 |
| tree | b8920bdf70fb621b3859cae826b2030b5df66a3e | |
| parent | 732cd1277645c81e98a3295f858a8ae1fbc986e9 [diff] |
[roll third_party/pigweed] pw_assert_log: Fix Soong rules The the Soong pw_assert_log_defaults cc_defaults was incorrectly using pw_log_null as the log backend. This redirects all PW_LOG* calls to a no-op function, breaking PW_CHECK, PW_ASSERT and friends who depend on that. This would mean that code continued executing after a crash! Do not let defaults inject backends, especially the pw_log_null backend. Original-Bug: 324266698 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/190602 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: bb1870ce1c8d99a..8b408829fcd8b9d Roller-URL: https://ci.chromium.org/b/8755970041828064817 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I875fb71d4918b1e6b7ceb02ff9e8e260fa58e22b Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/192785 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.