roll: third_party/pigweed Reland "docs: Enable Doxylink" This is a reland of commit ed98e925da046f4ecfe802e890efb0258253f256 https://pwrev.dev/299993 was reverted because the local macOS ARM docs build was failing. As of https://pwrev.dev/309760 that tryjob coverage gap is now filled. The root issue was the hardcoded tagfile path in //docs/doxygen/Doxyfile that change #299993 introduced. This hardcoded path is invalid on macOS ARM. The new OUTDIR feature introduced in https://github.com/TendTo/rules_doxygen/pull/30 lets us configure this path properly for all host OSes. Original-Bug: 434937497 Original change's description: > docs: Enable Doxylink > > Doxylink is a lightweight Sphinx extension that makes it easy > to link from the main pigweed.dev site (powered by Sphinx) > to the pigweed.dev/doxygen subsite (powered by Doxygen). > > Original-Bug: 426012010 > > Change-Id: I49c6c66a8bbb45dc05a47df0e526a5d5acf5a5a3 > Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/299993 > Pigweed-Auto-Submit: Kayce Basques <kayce@google.com> > Tests-Not-Needed: Kayce Basques <kayce@google.com> > Copybara-Verified: Copybara Prod <copybara-worker-blackhole@google.com> > Commit-Queue: Kayce Basques <kayce@google.com> > Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> > Reviewed-by: Armando Montanez <amontanez@google.com> Original-Bug: 426012010 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/309434 Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Original-Revision: 494717f520908dc9d351dc612b9741270d3f117d Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 4bdcd99f0c0c75..494717f520908d Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8707412130241585137 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I44e9630421442552c972c60f64282552fe871fb5 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/310655 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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.