roll: third_party/pigweed pw_rpc2: Set MallocNanoZone=0 on macOS for echo_test Under macOS sanitizers (such as AddressSanitizer), the sanitizer runtime reserves virtual memory early during startup, preventing macOS's nano malloc zone from reserving its fixed address range and causing libmalloc to log: malloc: nano zone abandoned due to inability to reserve vm space. Because echo_test captures combined output from the example client and server processes and compares it against expected output files, this warning interrupts the expected echo logs and causes the test to fail. Set MallocNanoZone=0 on macOS to disable nano zone initialization. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/500413 Original-Revision: 802a7cbb62b4cd48d1085541df2e30b899f31d64 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 8e2d22c29c2956..802a7cbb62b4cd Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8668164131596066641 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I333d6a3a768f2676413821f0f58bf5da6eadfaf3 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/500593
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/examples/+/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/examples
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.