Bill Janssen <janssen at parc.com> writes: > In that case, I think your idea of just hard-coding a path is probably > the right thing to do. I'll add a note that this is how you need to do > it if you are going to try "python setup.py build". Presumably the > binary then built with "python setup.py bdist" will install on a Windows > machine regardless of where OpenSSL is installed? Yes (though typically bdist_wininst for the Windows installer), but perhaps not for the reason you think. I think where there's probably a small disconnect here is that, there really isn't an OpenSSL "installed" on the end user's machine. Well, there could be, but Python isn't using it. The OpenSSL library is statically linked as part of the _ssl.pyd module, as it will be with your _ssl2.pyd module. (That's also why there is no OpenSSL to "find" in your setup even with Python installed - at least not any libraries you can use). In other words, both the standard and your extension module on Windows bring along their own OpenSSL. -- David
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4