Skip to content

Don't pass -Werror to ClangImporter's clang when Swift is used from LLDB #13293

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

Merged
merged 1 commit into from
Dec 6, 2017

Conversation

adrian-prantl
Copy link
Contributor

Don't pass -Werror to ClangImporter's clang when Swift is used from within LLDB.

This works a around search path problems caused by a module existing
in both the build/install directory and the source directory.

rdar://problem/35714074

@adrian-prantl
Copy link
Contributor Author

@swift-ci test

Copy link
Contributor

@jrose-apple jrose-apple left a comment

Choose a reason for hiding this comment

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

I'm still uneasy about this, but given that I can only think of one possible issue (relative search paths) and it's more unlikely than what we've been seeing, I won't block the change. I'd hope we can put this back some day, though.

// directory and the source directory.
if (!importerOpts.DebuggerSupport)
invocationArgStrs.push_back(
"-Werror=non-modular-include-in-framework-module");
Copy link
Contributor

Choose a reason for hiding this comment

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

Don't worry about keeping these in the same order. It's okay to put this after the fixed set of normal arguments.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought there was value in grouping all module-related options together.

Copy link
Contributor

Choose a reason for hiding this comment

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

Hm, okay, but then I'd rather move the whole section below the completely unconditional and uncategorized settings.

…ithin LLDB.

This works a around search path problems caused by a module existing
in both the build/install directory and the source directory.

<rdar://problem/35714074>
@adrian-prantl
Copy link
Contributor Author

@swift-ci smoke test and merge

1 similar comment
@adrian-prantl
Copy link
Contributor Author

@swift-ci smoke test and merge

@swift-ci swift-ci merged commit 68a4b43 into swiftlang:master Dec 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants