| commit | de71a346987b592414482e1044c6112cbc8bb751 | [log] [tgz] |
|---|---|---|
| author | Aaron Green <aarongreen@pigweed.infra.roller.google.com> | Sat Sep 14 02:29:39 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Sep 14 02:29:39 2024 +0000 |
| tree | f9ec425c148760c35fd06bf8671e4dbf97b38706 | |
| parent | 39a392e02023844bc3c30b5d2fee756b0f3cc1f9 [diff] |
roll: third_party/pigweed pw_fuzzer: Improve .bazelrc fuzzing support
This CL drops the fuzztest.bazelrc generated by FuzzTest, and instead
adds imports two new files from //pw_fuzzer: libfuzzer.bazelrc and
fuzztest.bazelrc. These facilitate adding fuzzing support to downstream
projects' .bazelrc files as well.
Additionally, this CL fixes up the Bazel support for FuzzTest. It uses
the //pw_toolchain/host_clang:asan_feature and adds a
//pw_toolchain/host_clang:fuzztest_feature instead of using FuzzTest's
approach of setting {c|link}opts directly.
Finally, this CL extands the same support for libFuzzer, in the form of
//pw_fuzzer/libfuzzer.bazelrc.
Original-Bug: b/347696410
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/216112
Original-Revision: 993b55e5321ceabcc80c82f25fd5d83f7b5045c4
Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 82759ccb711c3f..993b55e5321cea
Roller-URL: https://ci.chromium.org/b/8736857553213441665
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I0bb74e650fcb5db58f706c09f416012212f2757b
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/235678
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.