-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bcrypto fails to build on windows #48
Comments
related: kyokan/bob-wallet#142 @chjj any tips? |
This is a strange error:
My best guess is that this path is too long:
Windows can't handle really long path names. This problem is worsened by older releases of bcrypto setting the msbuild option The good news is that I've removed the |
On a side note, I think we should consider distributing pre-built binaries for windows and apple. Building on windows and apple is an absolute nightmare. Windows requires several gigabytes of disk space to install all of the VS build tools, and it's not something windows users typically have installed. Mac OSX Catalina is having disastrous issues with builds as well. So much so that dozens of programmers couldn't figure out the true source of the issue even after months of researching it. On the other hand, Linux and the BSDs just work. The compiler and build system is more often than not already installed. The compiler isn't some crazy Apple fork, and it doesn't require 100gb of disk space to install in the first place. I've been hoping for a node build system that just bundles vanilla clang & make for windows and apple (or auto-downloads & caches them). I feel like this would solve all of the build issues for windows and apple, and would allows us to switch to simple Makefiles instead of using gyp files. For more complex builds, maybe cmake would be added in the future. Maybe someday a zero-headache build system for node will be created, but I guess until then, the only option is prebuilds. |
I'll give it a try with master when I get a chance. Would there be anything else I could do to make it work with windows if that still fails? |
@faustbrian I'm a newb at development in Windows environment but learned last night that I could not build bcrypto unless git-bash was run as Administrator, dunno if that helps. |
To have it build with docs install instructions on OSX with "gpk rebuild" I had to add : *** => bcoin/node_modules/bcrypto/src/secp256k1/src/scalar_4x64_impl.h line 962 => #include "string.h" // *** monkey patch *** hth it seems memcpy is not declared per default with the OSX toolchain and perhaps same with WIN. |
|
Find here guys, for me setting python to version 2 worked.
after run https://stackoverflow.com/questions/29673365/fails-to-build-node-package-due-to-python |
Currently building bcrypto on Windows seems to fail, at least with GitHub Actions as I don't have a Windows machine at hand with a development environment to test it there.
The text was updated successfully, but these errors were encountered: