Skip to content

Conversation

@stuartmorgan-g
Copy link
Contributor

Description

Rather than macos/Flutter containing a mixture of files that should and
shouldn't be checked in, create clear locations for:

  • Files that are "owned" by Flutter, but should be checked in
    (Flutter/). This will contain files like the top-level Flutter
    xcconfigs, generated plugin registrants, etc.
  • Files that are generated by Flutter on the fly, and should not be
    checked in (Flutter/ephemeral/). This will contain Flutter SDK caches,
    the generated xcconfig, etc.

Also adds Flutter-owned Debug and Release xcconfig variants, in
preparation for PodSpec tooling.

Related Issues

None.

Tests

I added the following tests: None

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I signed the CLA.
  • I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
  • I updated/added relevant documentation (doc comments with ///).
  • All existing and new tests are passing.
  • The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require Flutter developers to manually update their apps to accommodate your change?

  • Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
  • No, this is not a breaking change.

(This is a breaking change, but only for macOS, which is explicitly unstable.)

Rather than macos/Flutter containing a mixture of files that should and
shouldn't be checked in, create clear locations for:
- Files that are "owned" by Flutter, but should be checked in
  (Flutter/). This will contain files like the top-level Flutter
  xcconfigs, generated plugin registrants, etc.
- Files that are generated by Flutter on the fly, and should not be
  checked in (Flutter/ephemeral/). This will contain Flutter SDK caches,
  the generated xcconfig, etc.

Also adds Flutter-owned Debug and Release xcconfig variants, in
preparation for PodSpec tooling.
stuartmorgan-g added a commit to stuartmorgan-g/flutter-desktop-embedding that referenced this pull request May 30, 2019
Reworks projects for the changes in
flutter/flutter#33608

Adds an extra layer of xcconfig indirection, so that there's a clear
distinction between the xcconfigs that are entirely human-managed, and
the configs that Flutter will manage (which is useful for Pod handling,
where Flutter needs to add configuration-specific xcconfig changes).
Copy link
Contributor

@jonahwilliams jonahwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Piinks Piinks added the tool Affects the "flutter" command-line tool. See also t: labels. label May 30, 2019
@stuartmorgan-g stuartmorgan-g merged commit 932200c into flutter:master May 30, 2019
@stuartmorgan-g stuartmorgan-g deleted the macos-flutter-dir-reorg branch May 30, 2019 20:43
stuartmorgan-g added a commit to google/flutter-desktop-embedding that referenced this pull request May 30, 2019
Reworks projects for the changes in
flutter/flutter#33608

Adds an extra layer of xcconfig indirection, so that there's a clear
distinction between the xcconfigs that are entirely human-managed, and
the configs that Flutter will manage (which is useful for Pod handling,
where Flutter needs to add configuration-specific xcconfig changes).
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants