Using xcodebuild, I have built (and archived) several variations of a framework with the following destinations: Step 4: realise swift-nio can't be built with BUILD_LIBRARY_FOR_DISTRIBUTION=YESĪll i want is this damned elastic swift as an XCF. (project or workspace, depending if you're using SPM or pods). Step 3: try xcodebuild archive -configuration Release -project "ElasticSwiftDRM.xcodeproj" -scheme "ElasticSwiftDRM" -destination 'generic/platform=iOS Simulator' -archivePath "./build/iphonesimulator.xcarchive" SKIP_INSTALL=NO BUILD_LIBRARY_FOR_DISTRIBUTION=YES (this is a fork I use but you can use the original, it's all the same because the issue is not in Elastic swift but one of its dependencies, swift-nio)
Make a framework project and add ElasticSwift from pods Hello, I have been pulling my teeth out for the past days trying to make this tool into an XCF to cut down on CI time cos caching SPM in azure devops pipelines takes forever (potato download speed etcetc)
0 kommentar(er)
