Set the scheme for the documentation build

[paulb777]

Description of the change

If there's one library the scheme matches the package, otherwise it auto-generates one for the package and generates a scheme for each product

Motivation

Fix failing spi doc build: https://swiftpackageindex.com/builds/FDA7B1D2-9174-4546-938F-30058E60E466

Type of change

Choose one: Bug fix

[andrewheard]

I'm fine with giving this a try since it's already not working but I am skeptical that it will fix it because:

swift package \
  --allow-writing-to-directory docc \
  generate-documentation \
  --target generative-ai-swift \
  --disable-indexing \
  --transform-for-static-hosting \
  --output-path docc
Building for debugging...
Build complete! (0.67s)
error: no target named 'generative-ai-swift'

[paulb777]

spi is using a command like this though:

 xcrun xcodebuild -IDEClonedSourcePackagesDirPathOverride=$PWD/checkout/.dependencies -skipMacroValidation  docbuild OTHER_DOCC_FLAGS=--emit-digest   -scheme generative-ai-swift -destination generic/platform=tvos

and that now succeeds for me locally

[andrewheard]

spi is using a command like this though:

 xcrun xcodebuild -IDEClonedSourcePackagesDirPathOverride=$PWD/checkout/.dependencies -skipMacroValidation  docbuild OTHER_DOCC_FLAGS=--emit-digest   -scheme generative-ai-swift -destination generic/platform=tvos

and that now succeeds for me locally

🤞 Maybe documentation_targets in the SPI Manifest really means schemes?

[andrewheard]

@paulb777 You were right! https://swiftpackageindex.com/google/generative-ai-swift/0.4.3/documentation/googlegenerativeai