Google Git
Sign in
pigweed/pigweed/examples/ba7dab073a8d6bc0891c9851c675c5ce37b15b15
commit
ba7dab073a8d6bc0891c9851c675c5ce37b15b15
[log]
author
Jonathon Reinhart <jrreinhart@pigweed.infra.roller.google.com>
Thu Jul 31 17:06:06 2025 -0700
committer
CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Thu Jul 31 17:06:06 2025 -0700
tree
12af266e41f67fd516331577eaf82e1b3eddc286
parent
50b1ec0a4bab574395a4d92ead9f1e654354a196 [diff]
roll: third_party/pigweed pw_build: Improve must_place.ld.h error output

This updates PW_MUST_PLACE, PW_MUST_PLACE_SIZE, and PW_MUST_NOT_PLACE to
provide more detailed error output, including the file and line number
of the offending invocation.

Note that LD's ASSERT() provides no means to format the error message
(or even concatenate two strings), so the best we can do is additional
ASSERT()s with the same conditional.

Example output:

ld.lld: error: Error: PW_MUST_NOT_PLACE found unexpected input section(s) matching pattern:
ld.lld: error: */libclock.*:*.o(.bss*)
ld.lld: error: at file, line:
ld.lld: error: src/main/main.ld
ld.lld: error: 18
ld.lld: error:
ld.lld: error: Error: PW_MUST_PLACE did not find required input section(s) matching pattern:
ld.lld: error: */libboot.*:*.o(.bss*)
ld.lld: error: at file, line:
ld.lld: error: src/main/main.ld
ld.lld: error: 19
ld.lld: error:
ld.lld: error: Error: PW_MUST_PLACE_SIZE found input section(s) with unexpected size:
ld.lld: error: *(.bss.shared_buffer)
ld.lld: error: at file, line:
ld.lld: error: ./src/main/shared_memory.ld
ld.lld: error: 8
ld.lld: error:

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309972
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: e48f9ae4f07a8dbf0249ea14c410b8e1dffaa39f

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: d2b4a3bd38573b..e48f9ae4f07a8d
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8707785080845949761
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I6b748e760c8bee068fcdce8b30d4d0ab588d5819
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/310114
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 12af266e41f67fd516331577eaf82e1b3eddc286
  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. .clang-tidy
  16. .gitattributes
  17. .gitignore
  18. .gitmodules
  19. .gn
  20. .pw_console.yaml
  21. activate.bat
  22. banner.txt
  23. bootstrap.bat
  24. bootstrap.sh
  25. BUILD.bazel
  26. BUILD.gn
  27. BUILDCONFIG.gn
  28. LICENSE
  29. MODULE.bazel
  30. navbar.md
  31. OWNERS
  32. pigweed.json
  33. pyproject.toml
  34. 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.