You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I try to run "python setup.py build" at windows7 command line, but an error happened: "_nanomsg_cpy/wrapper.c(4) : fatal error C1083: Cannot open include file: 'nanomsg/nn.h': No such file or directory."
The nanomsg is installed at C:\nanomsg, and I found the nn.h file is located at: C:\nanomsg\src
How can I let python konw the nanomsg path?
My enviroment is nanomsg-0.6-beta, python 3.4 32 bit, visual studio c++ express 2010, windows 7 64 bit.
Who can tell me how to do it? I'm a newer at python. thanks.
Best Regards!
The text was updated successfully, but these errors were encountered:
Is nanomsg installed at C:\nanomsg or just downloaded/checked-out/extracted there? I'm not really sure how Windows installs work these days, but i'd expect there to be an include directory somewhere, not just src.
I think you need to add a --include-dirs argument to your python setup.py build command, which would point to an include directory (containing nanomsg/nn.h. You might also need a library_dirs variable set somewhere. See also: https://docs.python.org/2/distutils/configfile.html
PR #54 adds wheel building on Windows to this repository. You can download the wheels now if you want to: just click on your Python version, click on artifacts, download the wheel and you can pip install it.
I try to run "python setup.py build" at windows7 command line, but an error happened: "_nanomsg_cpy/wrapper.c(4) : fatal error C1083: Cannot open include file: 'nanomsg/nn.h': No such file or directory."
The nanomsg is installed at C:\nanomsg, and I found the nn.h file is located at: C:\nanomsg\src
How can I let python konw the nanomsg path?
My enviroment is nanomsg-0.6-beta, python 3.4 32 bit, visual studio c++ express 2010, windows 7 64 bit.
Who can tell me how to do it? I'm a newer at python. thanks.
Best Regards!
The text was updated successfully, but these errors were encountered: