How is the extension built platform-specifically? #15183
Unanswered
filiptronicek
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there 👋!
The testing workflow in GitHub Actions only specifies the steps for building the
universal
target, but the extension is published, from what I can tell, to these following targets:linux-arm64
darwin-arm64
alpine-x64
alpine-arm64
win32-arm64
linux-armhf
win32-x64
darwin-arm64
linux-x64
as well as
web
. I'm curious about how we can build all of these ourselves and whether that code is available somewhere. I tried building platform-specific versions of Jupyter in a testing workflow, but those packages are turning out almost 2x larger than the ones you provide. I'm curious if I'm missing any optimizations or some script which helps with producing the artifacts.Beta Was this translation helpful? Give feedback.
All reactions