(This figure does not include writing the `CMakeLists.txt` files.) The approximate number of lines in the various set‐up scripts can serve as a rough comparison of how easy it is to run tests on each platform: PlatformĬonfigure Visual Studio install platform module maps, Swift, and ICU minor repairs additions to `PATH` run CMake test And you can search it’s source for os(Windows) or os(Android) to get a sense of some of the platform differences and what does and doesn’t work yet. You can see an example of a package being tested on all platforms here. ![]() You will need to supply a lot more build flags manually, because the compiler, CMake and SwiftPM haven’t yet been taught where to find everything either.Or else you have to build the whole toolchain from source. The necessary toolchains aren’t available at the official Swift site, so to install you have to do more work collecting the pieces (and figuring out where to find them in the first place).These platforms are still experimental and not officially supported.(I think this too is mostly concentrated around complex protocol hierarchies.) The compiler occasionally trips for Android where it wouldn’t for macOS or Linux, resulting in the need for either #if !os(Android) or code to be refactored. Apparently SwiftPM can also be used to compile source natively on Android. Both SwiftPM and CMake can cross‐compile from Linux. Of the core libraries, only FoundationNetworking has been giving me problems. (Not sure about variants besides Ubuntu though, if that is what you were referring to.)Īndroid works and some companies are using it in production. You will just find fewer third‐party development utilities for Linux. Linux has been officially supported and on par with macOS for some time now. I think it would also be good to know the status of Android and Linux as well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |