Build the libraries for distribution.

[JonSalerno]

Currently the project has not been set to build the libraries for distribution. If we set it to "Yes", then XCode will generate the necessary files for different versions of swift to interact with each other. Then when people update XCode they will no longer have to update the framework with it (Once that gets updated).

[MaxDesiatov]

Unfortunately, ABI stability will require us to keep API stability too, which we cannot guarantee at the moment. The API of XMLCoder is still evolving. We could consider enabling ABI and module stability after the release of XMLCoder 1.0 though.

[MaxDesiatov]

Additionally, XMLCoder maintains compatibility with Swift 4.2, while module stability is only available starting with Swift 5.1. As this library is not distributed as a binary, I'd rather keep compatibility with Swift 4.2 at the small cost of recompiling the project when a new Xcode version is released. Besides, I'd recommend the usage of SwiftPM integration of Xcode (available starting with Xcode 11, same version that introduced module stability by the way) instead of CocoaPods or Carthage. The SwiftPM integration in Xcode handles rebuilds for you automatically, as far as I understand.