Swift package generate-xcodeproj and binaryTargets in Package.swift

din · September 26, 2020, 8:19pm

Will it ever be possible to generate an Xcode project from a Package.swift which contains a reference to binaryTarget?

Currently it fails silently, and in the code it has this:

github.com

apple/swift-package-manager/blob/main/Sources/Xcodeproj/pbxproj.swift#L400


// FIXME: We should factor this out.
let productType: Xcode.Target.ProductType
switch target.type {
case .executable:
    productType = .executable
case .library:
    productType = .framework
case .test:
    productType = .unitTest
case .systemModule, .binary:
    fatalError()
}

// Warn if the target name is invalid.
if target.type == .library && invalidXcodeModuleNames.contains(target.c99name) {
    warningStream <<< ("warning: Target '\(target.name)' conflicts with required framework filenames, rename " +
        "this target to avoid conflicts.\n")
    warningStream.flush()
}

// Create a Xcode target for the target.

Is there any timeline to get this supported, or should generate-xcodeproj be avoided by developers that work with binary targets in their packages?

Steven0351 · September 26, 2020, 3:03am

I have this exact same issue. I extracted some C/C++ dependencies that I used to compile and had to vendor through my source repo into a binary Swift Package and now I'm unable to generate Xcode Projects that depend on it. It also prevents me from running tests for Apple platform targets since SPM itself can only run tests against macOS and Linux.

Steven0351 · September 26, 2020, 3:33am

I ended up opening an issue SR-13615

0xTim · September 28, 2020, 7:19am

You can use xcodebuild directly on a Package.swift without needing to generate a project first. That uses Xcode's built in SwiftPM support which should solve your issue

din · September 28, 2020, 7:22am

Sometimes it’s necessary to generate frameworks, especially given the fact that directly using xcodebuild sometimes does not see all public headers that some packages I use define. It is also important to be able to build frameworks directly because it’s faster to distribute in comparison to having bare .o files with bare swift modules. Also, it’s very important that sometimes direct xcodebuild does not generate swift modules for C targets in packages even though it does that when generate-xcodeproj is used.

Steven0351 · September 28, 2020, 1:37pm

In the SR ticket I linked I actually mentioned in my case xcodebuild is not working either. I get this issue:
multiple configured targets of <Generated_Scheme> are being created for iOS Simulator

They may be unrelated but unfortunately isn’t a workaround in my case.