So I am trying to understand the Swift build process, and I'm struggling to understand how exactly dynamic libraries are handled.
So for instance, in the C/C++ world, if I am linking against a dynamic library, I would need to link the build artifact (
.dylib) and I would also have to specify the header search paths (
-I argument) so that the compiler can understand the public interface of the library.
Is there a Swift analog to this? For instance, if I look at the
.build/debug directory for a SPM package which produced dynamic library products, I can see the
.dylib artifacts there, but it's not clear to me where the interfaces are defined.