Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move the bootstrap output dir inside the environment #7212

Merged
merged 1 commit into from
May 31, 2021

Conversation

mspang
Copy link
Contributor

@mspang mspang commented May 28, 2021

Putting it at out/ causes problems:

  1. Our scripts and docs use subdirectories of out/ as the build
    root to allow creating multiple output directories with different
    configurations. These directories are now nested inside the
    bootstrap dir which is likely to cause confusion.

  2. Using a single location in and out of docker breaks. The vscode
    docker moves the environment to work around these conflicts.
    Using a common build directory will cause similar breakage.

  3. Cleaning the environment without cleaning out/ results in errors.
    This indicates they should be co-located.

Move it to a sub-directory of the environment.

Tested by running scripts/bootstrap.sh

Putting it at out/ causes problems:

1) Our scripts and docs use subdirectories of out/ as the build
   root to allow creating multiple output directories with different
   configurations. These directories are now nested inside the
   bootstrap dir which is likely to cause confusion.

2) Using a single location in and out of docker breaks. The vscode
   docker moves the environment to work around these conflicts.
   Using a common build directory will cause similar breakage.

3) Cleaning the environment without cleaning out/ results in errors.
   This indicates they should be co-located.
@andy31415 andy31415 merged commit 2c81a99 into project-chip:master May 31, 2021
nikita-s-wrk pushed a commit to nikita-s-wrk/connectedhomeip that referenced this pull request Sep 23, 2021
Putting it at out/ causes problems:

1) Our scripts and docs use subdirectories of out/ as the build
   root to allow creating multiple output directories with different
   configurations. These directories are now nested inside the
   bootstrap dir which is likely to cause confusion.

2) Using a single location in and out of docker breaks. The vscode
   docker moves the environment to work around these conflicts.
   Using a common build directory will cause similar breakage.

3) Cleaning the environment without cleaning out/ results in errors.
   This indicates they should be co-located.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants