-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix .wasm
product paths for wasm32-unknown-none
triple
#7355
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
Conversation
Absence of this extension on produced binaries makes it inconvenient to work with triple, as you have to add that extension manually after the fact. For examples, HTTP servers frequently don't infer correct mime-type for these binaries, which confuses browsers that try to load these binaries.
@@ -3431,111 +3431,6 @@ final class BuildPlanTests: XCTestCase { | |||
XCTAssertMatch(executablePathExtension, "exe") | |||
} | |||
|
|||
func testWASITarget() throws { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved to Tests/BuildTests/CrossCompilationBuildPlanTests.swift
to make Tests/BuildTests/BuildPlanTests.swift
smaller and increase parallelization during testing, as separate XCTestCase
types can be parallelized, while multiple functions in XCTestCase
can't.
@swift-ci test |
@swift-ci test |
@swift-ci test windows |
…xd/wasm-unknown-none-ext
@swift-ci test |
@swift-ci test windows |
…#7355) Absence of this extension on produced binaries makes it inconvenient to work with triple, as you have to add that extension manually after the fact. For examples, HTTP servers frequently don't infer correct mime-type for these binaries, which confuses browsers that try to load these binaries.
…#7355) Absence of this extension on produced binaries makes it inconvenient to work with triple, as you have to add that extension manually after the fact. For examples, HTTP servers frequently don't infer correct mime-type for these binaries, which confuses browsers that try to load these binaries.
Absence of this extension on produced binaries makes it inconvenient to work with triple, as you have to add that extension manually after the fact. For examples, HTTP servers frequently don't infer correct mime-type for these binaries, which confuses browsers that try to load these binaries.