Google Git
Sign in
pigweed / pigweed / examples / 26f9caedef31e7e62769e512f93378e2863d6bad
commit26f9caedef31e7e62769e512f93378e2863d6bad[log] [tgz]
authorBen Lawson <benlawson@pigweed.infra.roller.google.com>Fri Sep 27 23:01:15 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Sep 27 23:01:15 2024 +0000
treec1b6afd298c2d562e6237bd99dcb8a856f2c302f
parent613b618b3ab9c317ca44f3fd9b946fc9f69b4978 [diff]
roll: third_party/pigweed Revert "pw_log_fuchsia: Add syslog dep to pw_log_fuchsia"

This reverts commit 42cff573c2016f8d0f78ef2f0db8cd9941601ab4.

Reason for revert: Causes bt-host creep budget to be exceeded in roller, thereby breaking the roller.

Original change's description:
> pw_log_fuchsia: Add syslog dep to pw_log_fuchsia
>
> This fixes bt_hci_virtual missing libsyslog.so.
>
> Change-Id: Icda8ffe16c05822f41d99ce3a7271752b51cf5ea
> Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/238552
> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
> Reviewed-by: Chase Latta <chaselatta@google.com>
> Docs-Not-Needed: Ben Lawson <benlawson@google.com>
> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com>
> Pigweed-Auto-Submit: Ben Lawson <benlawson@google.com>
> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>

TBR=pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com,android-build-ayeaye@system.gserviceaccount.com,benlawson@google.com,auto-submit@pigweed-service-accounts.iam.gserviceaccount.com,chaselatta@google.com

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/238513
Original-Revision: 300cd1ca16733e21346ee06de1fa1a46d301f6d3

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 8f18755dc9a225..300cd1ca16733e
Roller-URL: https://ci.chromium.org/b/8735602351292636881
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I932d2ece4c77314412721593c109a2403f585e53
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/238488
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: c1b6afd298c2d562e6237bd99dcb8a856f2c302f
  1. build_overrides/
  2. docs/
  3. examples/
  4. images/
  5. infra/
  6. libraries/
  7. targets/
  8. third_party/
  9. tools/
  10. .clang-format ⇨ third_party/pigweed/.clang-format
  11. activate.sh ⇨ bootstrap.sh
  12. .bazelignore
  13. .bazelrc
  14. .bazelversion
  15. .gitattributes
  16. .gitignore
  17. .gitmodules
  18. .gn
  19. .pw_console.yaml
  20. activate.bat
  21. banner.txt
  22. bootstrap.bat
  23. bootstrap.sh
  24. BUILD.bazel
  25. BUILD.gn
  26. BUILDCONFIG.gn
  27. LICENSE
  28. MODULE.bazel
  29. navbar.md
  30. OWNERS
  31. pigweed.json
  32. pyproject.toml
  33. README.md
README.md

Pigweed Sample Project

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!

Getting started

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

Environment setup

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

Building

All of these commands must be run from inside an activated developer environment. See Environment setup

One-shot build

To build the project, documentation, and tests, run the following command in an activated environment:

pw build

Automatically build on file save

Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:

pw watch

Typical workflow

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

More info and Examples

Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.