![]() There is -configuration debug and -configuration release and that is all. ![]() SwiftPM has no equivalent of custom schemes. The Xcode project will be completely ignored by any package clients. I haven’t tried any of this in the Xcode 12 betas to know if any of it is out of date.) (Disclaimer: This information relates to Xcode 11. Has anyone found an elegant solution to this problem? Ideally a solution that would also work nicely if I decide to add my Package to a CI system. Some tutorials suggest running scripts as a Git pre-commit hook, or maybe as a Scheme pre-action, but I would lose the nice integration of SwiftLint with Xcode's source code editor. But having to create 2 repositories for every Package also feels wrong. I also thought about creating a dummy project inside another Git repository that then depends on my Package. Also my dummy project would get included in every App that depends on my Package. But with this kind of circular reference, it feels like I'm doing it wrong. I tried creating a dummy Xcode project inside my Package's root directory, which would then reference the Package itself and add a Build-Phase script here. īut I still haven't found an easy way to run a Build-Phase script, like in my other Xcode projects. swiftpm directory which can then contain my Schemes. I found nothing about Schemes in the documentation, but I noticed that Xcode automatically creates a hidden. targets, products, build-settings, build-configurations.). While reading the SPM documentation, i found that many of the Xcode concepts I'm familiar with can be described in the Package.swift manifest (e.g. I'm now trying to add a Build Phase script to execute SwiftLint when I run my Package's unit-tests locally in Xcode. I'm trying to learn SPM by making a simple standalone Swift Package with Xcode 11.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |