google / google/XNNPACK

[Question] Contributing a Swift Package Manager build

Open
#8,938 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
2.5k
Forks
560
Avg merge
1d 6h
Merged PRs (30d)
163

Description

Hello,

I have been working on Swift Package Manager build of XNNPack, so far for Web Assembly (with options for scalar, simd, relaxed-simd). I plan to expand this to support at least arm64, maybe other targets too. Would it be interesting for the project for me to upstream this work? Or should I keep it in a fork?

The biggest potential challenge is that the downloaded deps (cpuinfo, pthreadpool, fxdiv) still need to be downloaded from somewhere, which isn't natively supported by SwiftPM unless they're also SwiftPM packages (I'm unaware of anyone vending these particular libraries currently via SwiftPM but they might exist).

Let me know what you think.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.