| commit | a27430ba8b1794611b94efcc17df27d2f06d6ee2 | [log] [tgz] |
|---|---|---|
| author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Jul 16 01:59:37 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 16 01:59:37 2024 +0000 |
| tree | 2ee2a99ef27a6b645ee72fb71f2d3aeb660c4da9 | |
| parent | e34d1b777de4ea6504945a9963cc133e4bbe3f8a [diff] |
roll: third_party/pigweed 8 commits 1bd9a79e9b80068 pw_ide: VSC status bar item for target selection 2955c4c9a1a048b pw_toolchain: Add tsan support for host builds 0e7b3303a2e5b35 pw_console: Replace placeholder page with real web a053780de153eee pw_web: NPM version bump to 0.0.20 4caae057c0fda46 pw_ide: Add IDE support refresh manager 28772428574c752 pw_web: Change repl keybinding to eval 6e2747685b1938f pw_web: Bundle console.ts, fix log source handlers 56eeafc862a5d9f pw_log: Log decoder timestamp cleanup https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: e3c08d776ad308d..1bd9a79e9b80068 Roller-URL: https://ci.chromium.org/b/8742295266961856801 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ic32cdc95ee04766a334cf6f33206e68264acdacb Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/223159 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.