So, #swiftPM build tool plugins that use .executableTarget are just hopelessly broken?
They seem to work fine in debug but will fail when archiving for iOS due to looking for the binary in the wrong place.
The workaround is to instead pre-build the binary and include it as a .binaryTarget, but 1.) gross, 2.) that's a whole another step that needs to happen before package resolution.

How to declare SPM packages that only support #visionOS:

platforms: [.custom("xros", versionString: “1.0”)]

#iOSDev #swift #SwiftPM

@nighthawk Sorry, I’m talking about using Package.swift #SwiftPM to finagle this. I can create frameworks in Xcode that have both Swift and ObjC code in it and export symbols from both. But I can’t seem to combine a Swift target and a ObjC target into a single Product in SwiftPM.

How do I create a library with #Swift #SwiftPM that has a mix of Swift and ObjC in it, and have it consumed as a single module?

Find yourself repeatedly importing the same modules over and over again?

Check out my latest article on how to combine multiple imports into one using a hidden #Swift attribute!

#iOSDev #SwiftPM #Modularization #Refactoring #CleanCode

https://www.fline.dev/organizing-my-swiftpm-modules/?source=iosdev.space

I love the way #SwiftPM handles library dependencies, and how it transforms them into static libraries when possible, while still allowing them to find their resources using `Bundle.module`.

I wish a similar strategy existed for Xcode projects that link static Frameworks. I want to hoist the static framework’s resources into my app bundle, and still allow the code in the library to find it.

Is there a way to do that without having to create another resource bundle that must be copied?

@steipete @KrauseFx spm is also resolving every time you change the branch (even when Package.resolved didn’t change). Is there any way to avoid this at least? #git #xcode #SwiftPM