static Linux SDK

[xavgru12]

Recently a static Linux SDK was introduced which does not require building swift for the target.
While this is not the yocto approach, this should work out of the box using Apple`s build scripts minimizing maintenance of this swift layer.

More info can be found here:
https://www.swift.org/documentation/articles/static-linux-getting-started.html

It could be another way to use swift inside yocto with: inherit static-swift

What do you think about this?
@jeremy-prater

[xtremekforever]

I could see having the libraries needed to statically compile Swift included in the dev packages and SDK so it's an option. But, this would not be the "normal" use case but a separate option if desired for simplicity or portability of binaries.

The hard part is I think that statically compiling requires passing --static-swift-stdlib to SwiftPM, so you'd need to have a destination file that points to swift_static inside the Yocto SDK so you can successfully do this. Not sure how cmake would do with that, but I imagine it is also possible.

[xavgru12]

@xtremekforever
Destination file? That is outdated, you mean installing the swift sdk with: swift install sdk <sdk_id>

Using it is: swift build --swift-sdk aarch64-swift-linux-musl
It does not require anything else.

I am not sure how to use the swift sdk with cmake. We may be the first ones to ever do that I am afraid.

[xtremekforever]

I was thinking that a destination file would be "simpler" to include and use in a Yocto SDK although it is outdated. But, I guess you could also build a Swift SDK into it by providing an info.json file, swift-sdk.json and toolset.json files in the Yocto SDK itself. Then, you could build for it using something like (assuming you installed your Yocto SDK at /opt):

swift build --swift-sdks-path /opt/my-yocto-sdk --swift-sdk my-yocto-sdk

And if the Yocto SDK includes the static libraries, then you could invoke the above with --static-swift-stdlib to compile statically for your target.

[xavgru12]

I was thinking that a destination file would be "simpler" to include and use in a Yocto SDK although it is outdated. But, I guess you could also build a Swift SDK into it by providing an info.json file, swift-sdk.json and toolset.json files in the Yocto SDK itself. Then, you could build for it using something like (assuming you installed your Yocto SDK at /opt)

This is where the swift-sdk-generator shines. I would not like to use something outdated which is not supported anymore.

I would provide the complete SDK artefact bundle in Yocto's generated SDK. The app developer is able to install/unpack Yocto's SDK and use the Swift SDK just like Apple suggests.