[Dependency Scanning] Process implicit imports of the source module first, emulating implicit builds

In case import resolution order somehow sometimes matters, it's prudent to process/resolve/locate implicitly-imported modules first.

Resolves rdar://113917657
This commit is contained in:
Artem Chikin
2023-09-21 12:35:59 -07:00
parent 9f61777eb0
commit c9c689aec1
10 changed files with 105 additions and 126 deletions

View File

@@ -12,16 +12,9 @@
import ImportsMacroSpecificClangModule
// CHECK: "directDependencies": [
// CHECK-NEXT: {
// CHECK-DAG: "swift": "ImportsMacroSpecificClangModule"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-DAG: "swift": "Swift"
// CHECK-NEXT: },
// CHECK-NEXT: {
// CHECK-DAG: "swift": "SwiftOnoneSupport"
// CHECK-NEXT: }
// CHECK-NEXT: ],
//CHECK: "swift": "ImportsMacroSpecificClangModule"
//CHECK-NEXT: },