How does Tuist determine the linking type of SPM dependencies?

[Ernest0-Production]

How does Tuist determine exactly how to link a target from Swift Package if I do not explicitly specify productType in PackageSettings?

1. Is it always a static library?

2. Does it take into account how many targets depend on SPM dependencies?

3. How exactly is the Resource Bundle compiled? I noticed a strange bug with the appearance of an incorrect value for the CFBundleSupportedPlatforms (iPhoneSimulator) key in SomePackage_SomeTarget.bundle/Info.plist. Asset validation failed Invalid CFBundleSupportedPlatforms value #6083
   This breaks the project's archiving :c

It seems that when pre-compiling SPM targets, it is important to somehow convey information about the platform.

[fortmarek]

Is it always a static library?

Yes, by default, if a product is only .automatic, we choose static. It gets more complicated if there are two products depending on the same target where one has a hardcoded .dynamic linking type, such as Alamofire. In those cases, we prefer the hardcoded type.

Does it take into account how many targets depend on SPM dependencies?

No, it does not.

How exactly is the Resource Bundle compiled?

During tuist cache, we generate only one resource bundle, which is why you see a simulator bundle. As noted in the issue, we currently don't officially support using tuist cache for release builds but we plan to fix that soon.