| commit | 7b463a60c6e56f289124579e5a1174368ce47874 | [log] [tgz] |
|---|---|---|
| author | Carlos Chinchilla <cachinchilla@google.com> | Thu Aug 20 14:26:35 2020 -0700 |
| committer | CQ Bot Account <commit-bot@chromium.org> | Fri Aug 21 19:25:17 2020 +0000 |
| tree | b2fb2692719d57276d51daa16c1477887ebc4ab2 | |
| parent | 47da2c33a224a5530528dbe86a01d1ddb2388898 [diff] |
Initial GN files Target-less GN files added, pointing to the required Pigweed GN files. Change-Id: Icca4062cfb7e485fdd2d1e5553a2c62654444f76 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/sample_project/+/16500 Reviewed-by: Armando Montanez <amontanez@google.com> Commit-Queue: Carlos Chinchilla <cachinchilla@google.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!
The preferred method to add the Pigweed source is to use git submodules and place the Pigweed source repository in third_party/pigweed. If you forked this repository, don't forget to run git submodule init and git submodule update.
The scripts bootstrap.bat for Windows, and bootstrap.sh for Unix systems call the respective Pigweed bootstrap scripts. Feel free to modify them to set up your development environment for the first time.
After the initial setup, use the activate.bat in Windows or activate.sh in Unix to enter the environment in a shell.
Make the project yours with your own banner. Create your own banner and place it in banner.txt.