-
Notifications
You must be signed in to change notification settings - Fork 304
SourceKit-LSP doesn't work with swift-for-wasm-examples
package
#1475
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
Comments
I'm not sure the report for this issue belongs to the examples repository, moving accordingly. |
swift-for-wasm-examples
package
Synced to Apple’s issue tracker as rdar://129662080 |
We previously always assumed that the project was being built for the host. Fixes swiftlang#1475 rdar://129662080
#1535 adds support for configuration options of cross-compiled projects. Once there’s an open source toolchain with that change (ie. a main development snapshot after June 29), you should be able to use it by placing a {
"swiftPM": {
"triple": "wasm32-unknown-none-wasm"
}
} This file essentially communicates the arguments that you pass to a |
We previously always assumed that the project was being built for the host. Fixes swiftlang#786 Fixes swiftlang#1475 rdar://129662080 rdar://113099964
@ahoppen Great work, thank you! |
We previously always assumed that the project was being built for the host. Fixes swiftlang#786 Fixes swiftlang#1475 rdar://129662080 rdar://113099964
Is there any way to configure the
swift-for-wasm-examples
package so that development with SourceKit-LSP works correctly?When opening
LadderFilter.swift
, an error appears forimport VultDSP
:And in the errors I get
In the output from SourceKit-LSP I can see:
It looks like the C flags in
Package.swift
are not used when building.I tried creating a
compile_flags.txt
with target and defines like in thePackage.swift
, but that doesn't seem to get respected.The text was updated successfully, but these errors were encountered: