1

So I have two repositories and so two Package.swift files. Packages have targets. Targets have dependencies. Situation:
P1.T1 depends on P2.T2
P2.T1 depends on P1.T2

So on the target level, there is no cyclic dependency. However, Xcode still thinks there is a cyclic dependency and reports an 'error cyclic dependency declaration found: P2 -> P1 -> P2'. It looks like it just checks dependencies on the package level without checking them on the target level.

1 Like
2

Yes, cyclic dependencies are not allowed at the package level, either.

3

:cry::cry::cry:

4

If there a fundamental reason for this? I can add two Xcode projects to the same workspace, and as long as there are no cyclical dependencies between targets I can have dependencies in both directions.

1 Like