Thinking about this just now I did think of one way to take myself out of the loop each update: We could have emsdk point directly at amazon S3 bucket for the arm64 binaries.. then it would just be a question of someone creating a PR to emsdk for each release (any interested party such as yourself could then do that part).
cheer, sam On Tue, Jan 17, 2023 at 1:47 PM Sam Clegg <s...@google.com> wrote: > I agree it would be nice to make this more automatic but we haven't found > an easy way to do this yet. > > Currently the process is that the arm64 binaries get built somewhere in > the amazon cloud (thanks Michael for setting this up) and then that sends > an email to me when it's done. I then have to manually download the > archive and push it up to the emsdk google cloud bucket where emsdk pulls > from. I then need to create a PR to bump the version in emsdk. > > Because this is a manual process with several steps (and honestly because > we don't have too many arm64 users yet) I sometimes take a while to get > around to doing it. > > If you can think of any way to automate this or speed this up that would > be great. > > (It looks like the builder has stopped running recently.. the last email I > got was for 3.1.24 back in October. Michael, do you have time to look into > that proximate problem). > > cheers, > sam > > On Tue, Jan 17, 2023 at 1:32 PM Brion Vibber <br...@pobox.com> wrote: > >> Hi all! >> >> I noticed that while there is now an arm64/aarch64 Linux binary available >> for emsdk, it's several versions behind: >> >> # macOS >> % ./emsdk install latest >> Resolving SDK alias 'latest' to '3.1.30' >> Resolving SDK version '3.1.30' to >> 'sdk-releases-dc1fdcfd3f5b9d29cb1ebdf15e6e845bef9b0cc1-64bit' >> >> # Linux on same machine >> $ ./emsdk install latest >> warning: 'latest' on arm64-linux may be slightly behind other >> architectures >> Resolving SDK alias 'latest-arm64-linux' to '3.1.21' >> >> What can people do as interested developers to help automate this process >> so that aarch64 Linux versions come out at the same time as x86_64 ones? Is >> there a need for hardware? Software? Developer time? Money? It'd be nice >> for this to be totally transparent to the developer installing the SDK, >> without requiring a lengthy local compilation of LLVM to get current >> versions. >> >> Thanks! >> >> -- brion vibber >> Software Architect >> Wikimedia Foundation >> >> -- >> You received this message because you are subscribed to the Google Groups >> "emscripten-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to emscripten-discuss+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/emscripten-discuss/CAFnWYTnFj6U%2Bws8MSZJ98Pq%2B2pC_WN7abhNpH4N9huUOF5fX7w%40mail.gmail.com >> <https://groups.google.com/d/msgid/emscripten-discuss/CAFnWYTnFj6U%2Bws8MSZJ98Pq%2B2pC_WN7abhNpH4N9huUOF5fX7w%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAL_va2-1F%2BOZEZaFribU7%3DLe-y2usFrJPp6mZDofwjaFo%3DL7Fw%40mail.gmail.com.
