| commit | e44ea8db4c1c232d5d57b722a49f62063f85d940 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Mar 27 01:56:15 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 27 01:56:15 2024 +0000 |
| tree | f41494933c8900252f6b8cf18313aada3e675cb5 | |
| parent | 08932ad3290b5ca0821b19fb21d6bdef0c924799 [diff] |
[third_party/pigweed] Roll 18 commits 3473c9118a43845 pw_log_tokenized: Define as cc_static_library e0888f672378e3e pw_router: Define as cc_static_library 68e898711ea85b8 pw_toolchain: Define as cc_static_library df4efa0243b5dba pw_result: Define as cc_static_library 595fd9562a8d905 pw_build_info: Add log function of GNU build ID 6ebdfaf68c2e080 pw_span: Define as cc_static_library d99ef2cf38ae998 pw_preprocessor: Define as cc_static_library 04fbfa382513335 pw_bluetooth_sapphire: Add emulator start workflow e9441715b774fc7 pw_polyfill: Define as cc_static_library 5c53b840a4ecd3f pw_rpc_transport: Define as cc_static_library d6d27ec27a71859 pw_function: Define as cc_static_library e0abef00c07545a pw_multibuf: Define as cc_static_library cb32298c56d1b71 pw_log_null: Define as cc_static_library 7cffdd83bfd413c pw_thread: Follow Soong guidance 7682e4abe456481 pw_allocator: Add allocation detail storage to Tra ebcc8c717f3980d pw_channel: Add loopback channel 72a1d6f484ecbd1 pw_toolchain: Remove unusued source set 16d3c47ab5a6d45 pw_status: Add StatusWithSize::size_or https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 55b88ef80fc2403..3473c9118a43845 Roller-URL: https://ci.chromium.org/b/8752355462294228977 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I7ddefed8a0337900b66dac5c41be1ed3db368eeb Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/200313 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.