| commit | e6a9ea219548e65f85fc943d5466c65d10339845 | [log] [tgz] |
|---|---|---|
| author | Wyatt Hepler <hepler@pigweed.infra.roller.google.com> | Tue Nov 05 08:59:00 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 05 08:59:00 2024 +0000 |
| tree | 356bd06d6156f96d4ecf90b3cdee8ebee578cded | |
| parent | a2e4d88ade7a0044a02fb840e33fed5200282155 [diff] |
roll: third_party/pigweed pw_unit_test: Separate target for status macros - Move the status macros (EXPECT_OK, etc.) to a separate build target so that tests that don't use pw_unit_test can use the macros with GoogleTest. - Rename pw_unit_test/status_test_matchers.h to pw_unit_test/status_macros.h since they are not GoogleTest matchers. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/246874 Original-Revision: 3cb8dc410fa5efcfc555f79bb533a08a72891612 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: e3bbf5895cabea..3cb8dc410fa5ef Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8732122171325288257 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I675c22996ef74a2ade75bbeb445506a97107b877 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/247015 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.