aaronm67
Windows support ?
Maybe use node-pre-gyp for distributing windows packages ? [building for windows is a pita]
I managed to get this library running in windows.just install node-gyp in windows as given here or here then install node-phash using npm.
@Rafi993 still can't install on windows. It seems there's a missing header file </usr/include/complex.h>. How to solve this issue?
It's too difficult to install this module, I've switched to a better module ghash which utilizes sharp for image decoding. It works pretty well!
@Rafi993 Obviously windows version has an issue.
P.S. node-gyp installed properly
e:\javascript\node-phash\deps\phash\ph_fft.h(32): fatal error C1083: Cannot open include file: '/usr/include/complex.h': No such file or directory (compiling source file ......\deps\pHash\ph_fft.c) [e:\JavaSc ript\node-phash\build\deps\pHash\phash.vcxproj]
Think problem is here inside deps/pHash/ph_fft.h
#include </usr/include/complex.h>
P.S. I changed dependency to file which you have and it's not compiled any more.
I changed source for pHash (using last one from pHash.org 0.9.4) and tried to build artifact, but now have another errors, might be you can help me with these errors.
Creating library e:\JavaScript\node-phash\build\Release\pHashBinding.lib and object e:\JavaScript\node-phash\build\Release\pHashBinding.exp phash.lib(pHash.obj) : error LNK2001: unresolved external symbol readdir [e:\JavaScript\node-phash\build\pHashBinding.vcxproj] phash.lib(pHash.obj) : error LNK2001: unresolved external symbol rewinddir [e:\JavaScript\node-phash\build\pHashBinding.vcxproj] phash.lib(pHash.obj) : error LNK2001: unresolved external symbol closedir [e:\JavaScript\node-phash\build\pHashBinding.vcxproj] phash.lib(pHash.obj) : error LNK2001: unresolved external symbol opendir [e:\JavaScript\node-phash\build\pHashBinding.vcxproj] e:\JavaScript\node-phash\build\Release\pHashBinding.node : fatal error LNK1120: 4 unresolved externals [e:\JavaScript\node-phash\build\pHashBinding.vcxproj]
@Muqito I made a fork and compile it on Win 10 64bit. You can try to use my fork, this is not final solution, but it's working for me.
I guess it is the commit that was made later that is causing the issue. node libraries with c/c++ bindings generally tend to have a problem in windows some permanent solution for this kind of bindings has to be found. so that we don't need to compile these dependencies manually but just do npm install.
