-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No target named 'swift-openapi-generator-arm64-apple-macosx15.0-debug-tool.exe' in build description
when doing --experimental-prepare-for-indexing
#8216
Comments
I started digging in to this issue, and while I don't know if I've got enough context to fix it completely I can state my findings. Building with swift-package-manager/Sources/Build/BuildManifest/LLBuildManifestBuilder.swift Lines 151 to 159 in 1d637b3
Because Obviously its not ideal, but I'm not sure the best approach to pair down the products while still building what is required. The other, much more minor thing is the swift-package-manager/Sources/Build/BuildManifest/LLBuildManifestBuilder+Product.swift Lines 149 to 154 in 1d637b3
Needs to take in to account the platform, i.e: fileprivate func executableName(
for product: String,
buildParameters: BuildParameters
) -> String {
if buildParameters.triple.isWindows() {
"\(llbuildNameWithoutExtension(for: product, buildParameters: buildParameters)).exe"
} else {
"\(llbuildNameWithoutExtension(for: product, buildParameters: buildParameters))"
}
} |
Yup, I was adding in the plugins but not the plugin tools that they invoke. I'll look for a way to do that. I assume we'll want to run them so they can generate code for proper indexing. |
Eliminate the special generatePrepareManifest and just reuse the real one and add a couple of checks for the target/product prepareForIndexing buildParameter instead. This then enables us to make sure we're doing a full build of the plugin tools so they can generate code to be properly indexed. Addresses swiftlang#8216 for openapi generator.
Eliminate the special generatePrepareManifest and just reuse the real one and add a couple of checks for the target/product prepareForIndexing buildParameter instead. This then enables us to make sure we're doing a full build of the plugin tools so they can generate code to be properly indexed. Addresses #8216 for openapi generator.
…ng#8230) Eliminate the special generatePrepareManifest and just reuse the real one and add a couple of checks for the target/product prepareForIndexing buildParameter instead. This then enables us to make sure we're doing a full build of the plugin tools so they can generate code to be properly indexed. Addresses swiftlang#8216 for openapi generator.
…8236) Back port of #8230 to release/6.1 Eliminate the special generatePrepareManifest and just reuse the real one and add a couple of checks for the target/product prepareForIndexing buildParameter instead. This then enables us to make sure we're doing a full build of the plugin tools so they can generate code to be properly indexed. Addresses #8216 for openapi generator.
Running
swift build --target HelloWorldHummingbirdServer --experimental-prepare-for-indexing
on the attached project fails withtestpackage.zip
The text was updated successfully, but these errors were encountered: