Xcode project with SPM dependencies

[SDGGiesbrecht (Jeremy David Giesbrecht)]

I tried to follow your steps on my own machine.

1. Directly copying and pasting your “Dependencies” manifest did not work. I had to add // swift-tools-version:4.2 to the very top. Did you just leave that out when you copied and pasted?

Other than that, the package and the generated “Dependencies” Xcode project both work properly.

The combined workspace runs into its trouble in the application target (meaning all the targets it inherits from the “Dependencies” project still work fine on their own). Since the application does not import CTulipIndicators, and SwiftTulipIndicators has not @_exported it, I think this all comes down to the general inconsistencies around import. You can read reams on the subject in this thread:

@_exported and fixing import visibility

I told @Jon_Shier I'd write something up on @_exported and visibility in general, so here it is. It's a bit of a brain dump, but I know if I wait until I have time to edit it it won't get posted for months. (That's already true, in fact; I've had this model kicking around my head for probably close to a year now.) So, thanks for the prompt, Jon. Today, if your Swift library "Foo" uses a library "Bar", the headers (or swiftmodule files) of "Bar" must be available to all clients of "Foo". This i…

Maybe @Aciid knows if there is anything the package manager could do to mitigate it? Maybe there is someplace Xcode would look by default where the Xcode target generated for a C‐dependent package target might put the module map?