Installing on Windows?

[paixaop]

Installing on Windows?

[paixaop]

Yes

Today the install process requires automake and make tools. You can try to compile under Cygwin. If you port the build stage to windows I will merge it in.

Pedro

On Aug 6, 2015, at 10:38, Scott [email protected] wrote:

Running npm install sodium doesn't work on Windows. Essentially, it says make not found and aborts.

This will probably require installing libsodium separately first (do we need to install libsodium-net and grab the dll?). I don't know.

—
Reply to this email directly or view it on GitHub.

[squirrelsama]

@paragonie-scott I also have a need for MingGW-less Windows builds. Does it sound unreasonable to pull down the pre-built Windows binaries from https://download.libsodium.org/libsodium/releases/ ? Do you know of any other native modules that do this? It might be against the node-gyp way to not compile from source, but it might be simpler to accomplish what we need that way. I'm gonna take a look at either anyway and see what I come up with.

[paixaop]

Today the automake is a way around getting the right compilation defines so that libsodium compiles in each platform. If you get libsodium to compile on your windows machine send me a copy of your Makefile, and I'll see if I can include it in the compilation process

[tommitytom]

I notice this has been closed, yet there appears to be no clear way on how to get this working on Windows. Has this actually been resolved?

[paixaop]

You can now use a binary distribution of the libsodium library and node sodium will bypass sodium compilation on windows and other platforms.
Check the Manual Build section of the Readme

[creshal]

NPM deletes the sodium folder between failed builds, so if the automatic build fails, you never get a folder to drop the binary distribution into. So this doesn't really work. Is there a way to specify a binary folder in an outside location?

[paixaop]

@creshal for the time being you can download the source from github and run make manually.

[creshal]

That compiles, after some changes to the makefile (I'll make a pull request for that once everything works), but now Node throws a "cannot find module" error when trying to load sodium or run Mocha:

module.js:568
  return process.dlopen(module, path._makeLong(filename));
             ^


Error: Das angegebene Modul wurde nicht gefunden.
\\?\C:\Users\creshal\Desktop\foo\app\node_modules\sodium\build\Release\sodium.node
at Error (native)
at Object.Module._extensions..node (module.js:568:18)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (C:\Users\creshal\Desktop\foo\app\node_modules\sodium\lib\sodium.js:16:15)
at Module._compile (module.js:541:32)
at Object.Module._extensions..js (module.js:550:10)

The file definitely exists, however.

Edit: Okay, the error message was confusing. I think. Compilation only works with a dynamically linked libsodium.lib; and then needs libsodium.dll both in the manual build folder during compilation and in %PATH% at run time. Some tests still fail, but those failures seem to be in native code and thus a problem of libsodium itself.

I'll prepare a pull request with an updated readme, Makefile (needs to set msvs_version) and binding.gyp.

Edit 2: Made one pull request for each the Windows and the test suite fixes; that should settle this topic.