Google Git
Sign in
chromium / chromiumos / config / 9e7939c97fa26e61d32c972d036d38421889f063
commit9e7939c97fa26e61d32c972d036d38421889f063[log] [tgz]
authorPrathmesh Prabhu <pprabhu@chromium.org>Tue Mar 10 22:59:52 2020
committerPrathmesh Prabhu <pprabhu@chromium.org>Tue Mar 10 23:03:30 2020
tree7b6781d409647e37f1231a3b6d59d657c4ae2061
parent73e913c0d26639b74d1bde65a47a5e3e9600fafb [diff]
Fix recipe_proto symlink name

BUG=chromium:1051694
TEST=prayers

Change-Id: Iba7c9d0fe0cd121316fb9df347cf29aefb05ecf6
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/config/+/2097351
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Commit-Queue: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Auto-Submit: Prathmesh Prabhu <pprabhu@chromium.org>
1 file changed
tree: 7b6781d409647e37f1231a3b6d59d657c4ae2061
  1. bin/
  2. go/
  3. infra/
  4. payload_utils/
  5. presubmit/
  6. proto/
  7. python/
  8. recipes/
  9. test/
  10. util/
  11. .gitignore
  12. .style.yapf
  13. .vpython
  14. generate.sh
  15. LICENSE
  16. PRESUBMIT.cfg
  17. pytype.cfg
  18. README.md
  19. requirements.txt
  20. setup_project.sh
README.md

Project Setup for Partners

  1. Before beginning verify that you have appropriate permissions to work with the project. This will usually mean having membership in the partner domain account that is configured for your project. Inquire with your local representative or Google contact if you need more information about the partner domain accounts configured for your project.

  2. Follow the Chromium OS Quick Start Guide through to the end of the “Get the Source” section. This guide walks you through installing prerequisites and syncing the public Chromium OS source code into a $SOURCE_REPO directory. This step pulls down a lot of code and could take up to an hour.

  3. Verify the name of your $PROGRAM and $PROJECT with your local representative or Google contact. These values will be used in the command below.

  4. Run the following command to sync your $PROGRAM and $PROJECT from within your chromiumos checkout in the $SOURCE_REPO/src/config directory:

    ./setup_project.sh $PROGRAM $PROJECT

    This command will execute a number of steps including checking out your program and project and other related repositories, symlinking a local manifest, and finally doing a full chromiumos sync.

  5. The $SOURCE_REPO/src/config/bin directory contains utilties for working with your project. Add the directory to the end of your PATH. You will probably want to add this configuration in your ~/.bashrc file or other appropriate location so you don't have to repeatedly set the PATH:

    export PATH=$PATH:$SOURCE_REPO/src/config/bin

If you got to this point without an error you are set up to start working on your project.

Working with Projects for Partners

After setting up your project you'll want to note the location of several important repositories within the checkout:

  • src/config: The repository that contains this README.md file. This repository contains the higher level framework including protocol buffer definitions, configuration language constructs, constraint checking code, and binaries for performing tasks.
  • src/program/$PROGRAM: The repository that defines the program of your project. This repository defines the constraints that your project follows.
  • src/project/$PROGRAM/$PROJECT: The repository that defines your project. This repository defines your project design under the constraints of the program it belongs to.

Partners will rarely propose changes to src/config and occasionally propose changes to src/program/$PROGRAM. The bulk of a partner's work will occur in in src/project/$PROGRAM/$PROJECT.