# WebAssembly + SwiftPM

**URL:** <https://forums.swift.org/t/webassembly-swiftpm/34343>\
**Category:** Package Manager\
**Tags:** packagemanager, webassembly\
**Created:** [March 6, 2020, 12:03am UTC](https://forums.swift.org/t/webassembly-swiftpm/34343 "2020-03-06T00:03:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kateinoigakukun](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/kateinoigakukun/32/16706_2.png) [@kateinoigakukun](https://forums.swift.org/u/kateinoigakukun)\
**Post date:** [March 6, 2020, 12:21am UTC](https://forums.swift.org/t/webassembly-swiftpm/34343/2 "2020-03-06T00:21:33Z")

</div>

SwiftPM with WebAssembly works well with that patch.

I already used SwiftPM to build a Swift project which is targeting for `wasm32-unknown-wasi` [GitHub - swiftwasm/JavaScriptKit: Swift framework to interact with JavaScript through WebAssembly.](https://github.com/kateinoigakukun/JavaScriptKit)

WebAssembly doesn't support linking multiple modules **at runtime** but wasm-ld which is a relocatable object file linker can link multiple modules **at build time**.

Now, Swift for WebAseembly depends on WASI and wasi-sysroot as SDK, but it's not installed in fixed absolute path, so users need to pass `--sysroot` flag when building.  
In addition, when exporting or importing symbols with host environment, users need to pass additional flags to allow undefined symbol at link time and to export specific symbols.  
(e.g. [https://github.com/kateinoigakukun/JavaScriptKit/blob/master/script/build-package.sh](https://github.com/kateinoigakukun/JavaScriptKit/blob/master/script/build-package.sh))

FYI: [Wasm Support - #14 by kateinoigakukun](https://forums.swift.org/t/wasm-support/16087/14)

---

_[View the full topic](https://forums.swift.org/t/webassembly-swiftpm/34343)._
