warning: Could not read SDKSettings.json for SDK #110
Comments
|
Please let me know if these warnings cause any issues for you, otherwise they're harmless and can be ignored. |
|
No issue other than making it harder to read the useful content in the build log output without filtering all these lines. Is there a simple work around like dropping an empty |
|
@MaxDesiatov @toffaletti I did a little research today about this issue and found that this I tried a very minimal file to see what would work to just silence the warning. Including the following content in {
"SupportedTargets": {},
"Version": "0.0.1",
"CanonicalName": "linux"
}Is it worth including this file by default in the generated SDKs to silence this warning and make the output cleaner? It seems like this is a feature of swiftpm now and unless it's removed, it's going to search for the file whenever cross-compiling is happening. In my SDK I'm adding this empty file to make the compilation output cleaner. It doesn't hurt anything although it's annoying that it has to be there just to make the warning go away. |
|
The warning is now suppressed in the main branch toolchain swiftlang/swift-driver#1619 |
I know that the warnings about the `SDKSettings.json` file were fixed in Swift 6.1 and later and that issue #110 was closed. However, we are still generating Swift SDKs for 5.9, 5.10, and 6.0 which all give the warnings. So, my suggestion is to generate this `SDKSettings.json` file for versions older than 6.1, similar to how the the Linux Static Swift SDKs do it. Here is the file that comes in the `swift-6.0.3-RELEASE_static-linux-0.0.1` Swift SDK for example: ```json { "DisplayName": "Swift SDK for Statically Linked Linux (x86_64)", "Version": "0.0.1", "VersionMap": {}, "CanonicalName": "x86_64-swift-linux-musl" } ``` Taking inspiration from this, I am generating a similar file for Swift SDKs created by the generator: ```json { "CanonicalName" : "x86_64-swift-linux-gnu", "DisplayName" : "Swift SDK for Ubuntu Jammy (x86_64)", "Version" : "0.0.1", "VersionMap" : { } } ``` The ordering is not the same due to how `JSONEncoder()` sorts things, and the formatting is a little different too due to `.prettyPrinted`, but it works just the same. And, the "warning: Could not read SDKSettings.json for SDK at: <path>" warning is successfully suppressed. This really is a minor change that is more "quality-of-life" then adding any functionality. But, not having those warnings printed when using the generated Swift SDKs are used is a nice to have.
custom SDKs generated with
swift-sdk-generatorcauseswift buildto repeatedly output this warning:This can be seen in logs from other issues:
#12
#27
The text was updated successfully, but these errors were encountered: