Skip to content
This repository was archived by the owner on Apr 21, 2025. It is now read-only.

Conversation

@stuartmorgan-g
Copy link
Contributor

@stuartmorgan-g stuartmorgan-g commented Jun 10, 2020

Apparently goma builds don't preserve file case, causing lots of warnings about non-portable include paths. This eliminates ~249,000 warnings for the Windows Host Engine builds, making the log file several orders of magnitude smaller and making it usable when opened in the browser.

Addresses most of flutter/flutter#59199

# goma compilation doesn't preserve file case, so don't warn about
# case-mismatches.
default_warning_flags += [
"-Wno-nonportable-include-path",
Copy link
Contributor

Choose a reason for hiding this comment

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

On second thought, why not just replace add this unconditionally on Windows? It feels odd that the TU will get different flags based on whether or not goma is used. You call though.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The issue is specific to goma AFAICT, and leaving it this way means we'll still get warnings locally for legitimate case mismatches. It seems like it would be a shame to have no way of getting warnings for things that are legitimately incorrect.

@stuartmorgan-g stuartmorgan-g merged commit b445ea3 into flutter:master Jun 11, 2020
@stuartmorgan-g stuartmorgan-g deleted the windows-goma-include-case-warning branch June 11, 2020 16:14
chinmaygarde pushed a commit to chinmaygarde/flutter_buildroot that referenced this pull request May 4, 2021
Apparently goma builds don't preserve file case, causing lots of warnings about non-portable include paths. This eliminates ~249,000 warnings for the Windows Host Engine builds, making the log file several orders of magnitude smaller and making it usable when opened in the browser.

Addresses most of flutter/flutter#59199
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants