At the moment VDC can only construct versioned documentation for targets that it can build. This means that it can't be used in situations where documentation for a package's products must be compiled across multiple machines (e.g. a package with platform-specific products such as SwiftCrossUI's backend products).
If VDC could take prebuilt archives as input then it'd be much easier to drop it into SwiftCrossUI's existing documentation build pipeline (which is rather complicated).
At the moment VDC can only construct versioned documentation for targets that it can build. This means that it can't be used in situations where documentation for a package's products must be compiled across multiple machines (e.g. a package with platform-specific products such as SwiftCrossUI's backend products).
If VDC could take prebuilt archives as input then it'd be much easier to drop it into SwiftCrossUI's existing documentation build pipeline (which is rather complicated).