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.

Sign up for GitHub

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

Jump to bottom

Add a feature to always include all headers as inputs to SwiftCompile actions, even when using explicit modules #1249

Merged
merged 1 commit into from
Jun 21, 2024
Merged

Add a feature to always include all headers as inputs to SwiftCompile actions, even when using explicit modules #1249

merged 1 commit into from
Jun 21, 2024

Commits on Jun 21, 2024

  1. Add a feature to always include all headers as inputs to SwiftCompile… 

    … actions, even when using explicit modules

When building with explicit modules, Swift compilations do not require any of
the headers to be present on disk, because the AST contains all the necessary
information (save for a bug(?) in `canImport` which fails if the headers aren't
also present). However, other tooling may want to inspect compilation
actions and have access to those headers.

This feature is a no-op for implicit module builds, since the headers are always
included to begin with, and it is off by default.

PiperOrigin-RevId: 461668350
(cherry picked from commit 81f7b54)
Signed-off-by: Brentley Jones <github@brentleyjones.com>
    @allevato @brentleyjones
    allevato authored and brentleyjones committed Jun 21, 2024
    Configuration menu
    Copy the full SHA
    95522d4 View commit details
    Browse the repository at this point in the history