roll: third_party/pigweed pw_elf: Add Python ELF image builder Adds a general-purpose Python library for programmatically building ELF32 and ELF64 files from scratch. While primarily intended for bare-metal crash coredump generation, the library is generic and can be used to construct any custom ELF. Supports adding: - Memory regions / loadable segments (with custom alignment constraints) - Architectural note segments / notes Original-Bug: 518889679 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/413112 Original-Revision: 44d79e3e65373d7fb6eebdb5fb0fccff801e92fb Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 711aa6418b09c0..44d79e3e65373d Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8679503491348534289 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ie84637671d11b65ba0484e2f61e7aed471877f04 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/419464
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.