Skip to content

WASI: Make some sources unavailable in CF CMake #3038

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

Merged
merged 1 commit into from
Aug 12, 2021

Conversation

MaxDesiatov
Copy link
Contributor

CFBundle, plugins, preferences, streams, and run loops are not available when compiling to WASI/Wasm because of the lack of a meaningful filesystem access and multi-threading. These sources files should be excluded from the build in CoreFoundation/CMakeLists.txt when compiling for that platform.

@MaxDesiatov MaxDesiatov requested a review from millenomi August 12, 2021 13:41
@MaxDesiatov
Copy link
Contributor Author

@swift-ci please test

@millenomi
Copy link
Contributor

There are a bunch of services tied to e.g. Bundle.main; do they need to be excluded from the build?

@millenomi millenomi merged commit e10529d into main Aug 12, 2021
@MaxDesiatov MaxDesiatov deleted the maxd/cf-wasi-unavailable branch August 12, 2021 22:43
@MaxDesiatov
Copy link
Contributor Author

I have a stub implementation of Bundle.main in the fork that doesn't rely on CoreFoundation, that will come in a separate PR.

@millenomi
Copy link
Contributor

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