| commit | 2879975bfef81761a7c45bc79949c372ebb4b446 | [log] [tgz] |
|---|---|---|
| author | David Gilhooley <dgilhooley@pigweed.infra.roller.google.com> | Tue Sep 12 14:46:57 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 12 14:46:57 2023 +0000 |
| tree | 5757857c9fc5b9d8d76c8f020d8505bcb5e4eb32 | |
| parent | c42a2c8dd9b1a393f20b81c9300e8ef4186e3d58 [diff] |
[roll third_party/pigweed] pw_chre: Add barebones CHRE NOTE: This is a very work-in-progress implementation. Add GN rules for the CHRE codebase into //third_party/CHRE. This also adds a pw_chre_PLATFORM_BACKEND gn argument for the platform backend for CHRE. Add a pw_chre directory that includes all of the class and function definitions required to compile CHRE. Some of this connects to pigweed functionality, some of it is stubbed out. //pw_chre:chre_simulator uses pw_system to run CHRE on pigweed on the host, and it compiles in a number of CHRE's example nanoapps. There is enough functionality that these nanoapps are able to run. Original-Bug: 294106526 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/162510 https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: ef447ae6f95cab0..f210a064bf6d67f Roller-URL: https://ci.chromium.org/b/8770150885417481937 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I89d476e84f1b5d0730d331078c2e2fce69a4e70c Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/sample_project/+/170590 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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. Once that is done, you can clone this project and all required git submodules with the following command:
git clone --recursive https://pigweed.googlesource.com/pigweed/sample_project
If you already cloned but forgot to include --recursive, run git submodule update --init to pull all submodules.
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/docs/gen/docs/html/index.html.