Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Support / documentation for Windows #105
At minimum, we should document setting up and using the Windows Subsystem for Linux, but I'd also like to support "real" Windows. This is unfortunately a fairly big hassle, since node-gyp and Windows don't get along as well as they could, and running node on Windows is kind of awkward at the best of times. Or maybe I'm just out of touch with the platform, so things feel harder than they should
Notes on the Linux/windows install:
Here's what I've been able to piece together so far for the "real Windows" install on a Windows 10 VM:
Install C++ build tools:
If you do have Visual Studio, you need to ensure that you've installed the Common Tools for Visual C++. You can either re-run the installer, or open VS and try to create a new C++ project that targets Windows, which will open the installer for you. Make sure the box for the Common Tools for Visual C++ is checked. After the installation, open a Command Prompt or Git Bash and run
If you do not have Visual Studio installed, open a Command Prompt (or Git Bash) as an Administrator and run
So, I managed to get aleph to install on windows (outside of the linux subsystem) with some gross hacks, mostly related to building node-webcrypto-ossl.
Building node-webcrypto-ossl required downloading a 64-bit binary OpenSSL 1.0.2 package from here, installing it to
Once I figured that out, I was able to clone aleph and build it with a couple changes:
Then I could run
All of this is to say that Windows support doesn't require that many changes, apart from the webcrypto stuff. If / when that gets fixed, we should be able to support real Windows without too much fuss.