Skip to content

Conversation

@kateinoigakukun
Copy link
Member

There is no reason to limit Embedded Swift to only the non-threads variant. The limitation made some tests in JavaScriptKit a bit more complicated, see e.g. https://github.com/swiftwasm/JavaScriptKit/pull/443/files#diff-2c1174f0c456f8536c09dce2f943c43287a6a207ef08054d6aeddf5f00efa040R86

There is no reason to limit Embedded Swift to only the non-threads
variant. The limitation made some tests in JavaScriptKit a bit more
complicated, see e.g. https://github.com/swiftwasm/JavaScriptKit/pull/443/files#diff-2c1174f0c456f8536c09dce2f943c43287a6a207ef08054d6aeddf5f00efa040R86
Copy link
Contributor

@MaxDesiatov MaxDesiatov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, do Python build scripts in the toolchain already build for this triple? I genuinely don't know as I didn't check that previously

@MaxDesiatov
Copy link
Contributor

@swift-ci test

@kateinoigakukun
Copy link
Member Author

build-script still doesn't build swift-sdk for the target but swiftwasm/swiftwasm-build does.

@kateinoigakukun
Copy link
Member Author

@swift-ci test

@kateinoigakukun kateinoigakukun enabled auto-merge (squash) September 11, 2025 06:33
@MaxDesiatov
Copy link
Contributor

@swift-ci test

@kateinoigakukun kateinoigakukun merged commit a1aa3db into swiftlang:main Sep 11, 2025
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants