Static/dynamic library products

[krzyzanowskim]

Resolves #159

This workaround Xcode Cloud builds (due to longstanding Xcode Cloud bug that can't build and link dynamic dependency properly)

[krzyzanowskim]

who's in power to merge it?

[SplittyDev]

Is there a way to give the user a choice? Not sure if static linkage should be the default

[davdroman]

@SplittyDev let me know if this solution looks sensible to you.

[SplittyDev]

@davdroman LGTM

I checked again, apparently SPM decides whether to link dynamically or statically automatically if linkage is left unspecified, so providing all three options seems to be the best option.

I'm not sure whether the static entry is needed, though. Afaik, static linkage is the default in Swift, so adding an entry for dynamic linkage should be enough to provide both. Providing both Introspect and Introspect-Static shouldn't be necessary, unless I'm missing something. Generally it isn't easy to find good information on that though, so I might be wrong.

[krzyzanowskim]

@SplittyDev static is the whole point of this change because automatically it happen to go dynamic and Xcode build fail

Xcode Cloud bug that can't build and link dynamic dependency

[davdroman]

Great stuff. I'll merge this as soon as the CircleCI situation is sorted (#179).

[SplittyDev]

@SplittyDev static is the whole point of this change because automatically it happen to go dynamic and Xcode build fail

Xcode Cloud bug that can't build and link dynamic dependency

You're absolutely right, I got this wrong at first. Great change, thanks for the PR!

[joelpoloney]

This is no longer blocked by CircleCI FYI.

[davdroman]

Hi @krzyzanowskim. 0.2.0 is now out and includes this change. Please let us know at some point whether this fixed your Xcode Cloud issues. Thanks!