FIR JS: fix klib matching in fir dependencies
use file paths for more reliable matching, since klib-based libs do strange things with libraryName
This commit is contained in:
+2
-2
@@ -64,7 +64,7 @@ class KlibBasedSymbolProvider(
|
||||
return resolvedLibrary.library.packageMetadataParts(packageStringName).mapNotNull {
|
||||
val fragment = getPackageFragment(packageStringName, it)
|
||||
|
||||
val libraryPath = Paths.get(resolvedLibrary.library.libraryName)
|
||||
val libraryPath = Paths.get(resolvedLibrary.library.libraryFile.path)
|
||||
val moduleData = moduleDataProvider.getModuleData(libraryPath) ?: return@mapNotNull null
|
||||
val packageProto = fragment.`package`
|
||||
|
||||
@@ -94,7 +94,7 @@ class KlibBasedSymbolProvider(
|
||||
}
|
||||
|
||||
resolvedLibrary.library.packageMetadataParts(packageStringName).forEach {
|
||||
val libraryPath = Paths.get(resolvedLibrary.library.libraryName)
|
||||
val libraryPath = Paths.get(resolvedLibrary.library.libraryFile.path)
|
||||
val fragment = getPackageFragment(packageStringName, it)
|
||||
|
||||
val nameResolver = NameResolverImpl(
|
||||
|
||||
Reference in New Issue
Block a user