linusdm
Building for Windows with burrito, with sqlite3, Nx, Exla, etc
I’m trying out burrito. It seems to fit my needs to cross-compile a Phoenix application into a single self-extracting binary for Windows.
Are there any problems to be expected with dependencies that are not written in Elixir? I see there are solutions for NIF based dependencies (I’m not an expert at all on this matter!). I’m not sure how transparently this is handled (and if it’s a good idea in the first place).
I’m thinking of these dependencies in particular:
- sqlite3 adapter
- Nx, Exla, Explorer, etc. (e.g. the typical dependencies to run inference on a neural network). This could also fallback to a non-accelerated version of the inference, without GPU support, but at least Nx should be available.
Or more in general: what will make a non-Elixir dependency compile successfully for Windows, with burrito? Or are all such dependencies expected to just work out of the box?
Most Liked
cmo
Righto. I think that is easier but I’m sure I’ve seen Jonaton mention that some things in the Nx ecosystem just won’t work on Windows. Best of luck ![]()







