Make sure to pass strict dependency include paths from the apple_common.Objc provider when compiling the explicit module for a target.
#675
Conversation
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
…mon.Objc` provider when compiling the explicit module for a target. Also clarify the purpose of the `compilation_context` argument in `swift_common.create_clang_module` and how it should and should not be used. PiperOrigin-RevId: 391067469 (cherry picked from commit a81c591) Conflicts: swift/internal/swift_clang_module_aspect.bzl
thii
force-pushed
the
make-sure-to-pass-strict-dependency-include-paths-from-the-apple_common.objc-provider-when-compiling-the-explicit-module-for-a-target
branch
from
751d8a5
to
07cc624
Compare
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
…mon.Objc` provider when compiling the explicit module for a target. Also clarify the purpose of the `compilation_context` argument in `swift_common.create_clang_module` and how it should and should not be used. PiperOrigin-RevId: 391067469
thii
deleted the
make-sure-to-pass-strict-dependency-include-paths-from-the-apple_common.objc-provider-when-compiling-the-explicit-module-for-a-target
branch
Also clarify the purpose of the
compilation_contextargument inswift_common.create_clang_moduleand how it should and should not be used.PiperOrigin-RevId: 391067469
(cherry picked from commit a81c591)
Conflicts:
swift/internal/swift_clang_module_aspect.bzl