Possibility to build with library evolution enabled

[flockoffiles]

In some situations it can be useful to compile Composable Architecture into a binary .xcframework and import it like that.

The current version of Composable Architecture can be built with -library-evolution option enabled, but the upcoming "protocol" branch no longer builds.

For previous discussions related to xcframeworks, please see: #890

Also see this comment discussion: #1283 (comment)

[mbrandonw]

And just to confirm, is building with library evolution a requirement in order to build an xcframework? My impression is that it is not, but that if you do you may get a warning about binary compatibility not being guaranteed.

[mbrandonw]

I'm not sure it's a considerable amount of work yet. We would definitely need to add another CI step to build the library with evolution on so that we can catch regressions. I'm just wanting to make sure I understand the full problem.

Do you know of an easy way to build for library evolution directly in Xcode? I only know how to do it from the command line, which is a bit of a pain.

[flockoffiles]

For an ordinary framework target, you set "Build Libraries for Distribution" to Yes under "Build Settings" in XCode.

For Swift Package, you probably need to specify the compiler option explicitly, just like you do when you enable concurrency warnings, etc.
(Have not done it myself, but here seems to be an example: https://github.com/apple/swift-package-manager/blob/main/Package.swift)
(Search for -enable-library-evolution)

[mbrandonw]

Took a stab at it here, but Stephen is out for a few days so may not merge it right away. But in the meantime can you point your project to that branch and let me know if it works?

[flockoffiles]

Yes. Trying...

[flockoffiles]

It builds fine now! You are SUPER awesome! :-)