I very much appreciate you going through our book! That’s wonderful to hear. But I’m sorry you’re running into issues here.
Indeed, as @lgmfred pointed out, Windows support in Nitrogen is experimental. That’s not to say it doesn’t work in windows (it does), but the build process is a bit tedious and, in my experience, rather fragile.
Generally speaking, the main takeaway from the windows guide (that @lgmfred so kindly linked) is that building Nitrogen projects initially tends to work better (at all?) when it’s being used in an msys (or git for windows) bash environment.
The latest can be gotten from gitforwindows.org.
Once installed (and you have Erlang installed), the
make commands should work.
Then, once the release is built, you can usually get away with starting the dev environment with the provided
start.cmd file. Then to enable the dev/hot code reloading, just make sure you run
sync:go() in the erlang shell.
This will work for a good long while until you need to add rebar dependencies, then you’ll likely want to run
make in your project from your msys environment again.
That said, all the examples in Build it with Nitrogen assume a Linux or Unix environment. We should probably include a line warning the user that running the book from Windows can be a bit more challenging.
If you’re comfortable slinging the msys/git-for-windows environment, then by all means, have at 'er (I find that environment challenging myself), or if you’re comfortable using linux subsystem for windows (or whatever it’s called), that could probably work (never really gave it much a try myself).
But I’d much rather myself spin up a Linux VM in VirtualBox and do everything from that or a remote shell than try wrastlin’ with Windows.