poddingue.bsky.social
@poddingue.bsky.social
This feels like ARM32 in 2013. Same struggles getting docker-compose on Raspberry Pi.
The ecosystem catches up. Eventually.
Full writeup: bit.ly/3KY3Quc
#RISCV #OpenSource #Tauri #devEco
The ecosystem catches up. Eventually.
Full writeup: bit.ly/3KY3Quc
#RISCV #OpenSource #Tauri #devEco
Adding RISC-V Support to Armbian Imager: A Tale of QEMU, Tauri, and Deja Vu | Bruno Verachten
Adding RISC-V Support to Armbian Imager: When "Straightforward" Becomes a 6-Hour Build
I wanted to contribute RISC-V support to Armbian's new Imager app (a Tauri desktop app). Adding a seventh platfo...
bit.ly
December 22, 2025 at 11:23 AM
This feels like ARM32 in 2013. Same struggles getting docker-compose on Raspberry Pi.
The ecosystem catches up. Eventually.
Full writeup: bit.ly/3KY3Quc
#RISCV #OpenSource #Tauri #devEco
The ecosystem catches up. Eventually.
Full writeup: bit.ly/3KY3Quc
#RISCV #OpenSource #Tauri #devEco
Tauri doesn't ship RISC-V binaries. If they did, every project building for RISC-V would save 6+ hours.
Plan: contribute RISC-V to Tauri's release workflow. Rising tide lifts all boats.
Plan: contribute RISC-V to Tauri's release workflow. Rising tide lifts all boats.
December 22, 2025 at 11:22 AM
Tauri doesn't ship RISC-V binaries. If they did, every project building for RISC-V would save 6+ hours.
Plan: contribute RISC-V to Tauri's release workflow. Rising tide lifts all boats.
Plan: contribute RISC-V to Tauri's release workflow. Rising tide lifts all boats.
Workarounds found:
- WebKit2GTK: use Debian trixie (now stable)
- NodeSource no RISC-V: Debian's nodejs works fine
- Build time: pre-built Docker image, then 10-20 min
But the real fix is upstream.
- WebKit2GTK: use Debian trixie (now stable)
- NodeSource no RISC-V: Debian's nodejs works fine
- Build time: pre-built Docker image, then 10-20 min
But the real fix is upstream.
December 22, 2025 at 11:22 AM
Workarounds found:
- WebKit2GTK: use Debian trixie (now stable)
- NodeSource no RISC-V: Debian's nodejs works fine
- Build time: pre-built Docker image, then 10-20 min
But the real fix is upstream.
- WebKit2GTK: use Debian trixie (now stable)
- NodeSource no RISC-V: Debian's nodejs works fine
- Build time: pre-built Docker image, then 10-20 min
But the real fix is upstream.
The answer is YES !
December 12, 2025 at 10:00 PM
The answer is YES !
Built native @next/swc for riscv64: 77min compile, 210MB binary, valid & loadable.
Next.js used WASM fallback. Why? riscv64 missing from the hardcoded platform map.
Peak dev irony: solved Rust compilation, crypto blockers, NAPI bindings, blocked by missing `riscv64` in JS object.
bit.ly/48iSyIy
Next.js used WASM fallback. Why? riscv64 missing from the hardcoded platform map.
Peak dev irony: solved Rust compilation, crypto blockers, NAPI bindings, blocked by missing `riscv64` in JS object.
bit.ly/48iSyIy
When Your Binary Builds But Next.js Won’t Use It: The riscv64 Platform Detection Story
After 77 minutes of watching cargo compile hundreds of Rust crates, I had a perfectly valid 210MB native SWC binary for riscv64. I packaged it correctly, placed it exactly where Next.
www.linkedin.com
November 25, 2025 at 10:59 AM
Built native @next/swc for riscv64: 77min compile, 210MB binary, valid & loadable.
Next.js used WASM fallback. Why? riscv64 missing from the hardcoded platform map.
Peak dev irony: solved Rust compilation, crypto blockers, NAPI bindings, blocked by missing `riscv64` in JS object.
bit.ly/48iSyIy
Next.js used WASM fallback. Why? riscv64 missing from the hardcoded platform map.
Peak dev irony: solved Rust compilation, crypto blockers, NAPI bindings, blocked by missing `riscv64` in JS object.
bit.ly/48iSyIy