HI team
I have a question with the SPM dependency management.
Lets say my SDK named ASDK. In the ASDK, I use BSDK(=> GSDK, HSDK, ISDK), CSDK, DSDK as its dependency.
For an application FAPP, the dev adds B SDK as its own dependency.
The graph likes:
When I build the application for the first time, it shows the errors like "Target has copy command from '....' '' but then now the error has gone...
Please help us with:
- How the SPM manage the deps graph for our case? Will it cause any conflicts?
- Does the dependency graph above cause any potential performance concerns? As after we implemented that, the Package.resolved has been added with all the dependencies of the BSDK. We are concerning it will cause issues or not.
- We want to actively control how many dependencies will be pulled by conditions. Is there anyway to do that? Like: for BSDK, we just want to load some of its dependencies and exclude the others as we dont use that feature.
1 post - 1 participant