README 1.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445
  1. Initial swig interface file
  2. Please send questions to support@wolfssl.com
  3. **Python Support**
  4. For Linux, OS X, or *nix
  5. 1) build wolfSSL with fpic on Linux, not needed on OS X
  6. ./configure --disable-shared CFLAGS=-fpic
  7. make
  8. sudo make install
  9. NOTE: if you want to use pbkdf pkcs #12 algorithm you should build CyaSSL with --enable-pwdbased:
  10. ./configure --disable-shared --enable-pwdbased CFLAGS=-fpic
  11. 2) start the example server from the root directory
  12. ./examples/server/server -d
  13. 3) run ./PythonBuild.sh from this directory it will
  14. a) build the swig wrapper file
  15. b) compile the swig wrapper and wolfssl wrapper files
  16. c) place them into a wolfssl shared library for python
  17. d) run runme.py which will connect to the wolfSSL server, write a
  18. string, then read the result and output it
  19. Windows only
  20. 1) Make sure the install path to wolfssl doesn't have any spaces anywhere in the
  21. directory path because swig doesn't like that
  22. 2) Have python for Windows installed, note install directory
  23. 3) Have swigwin installed, note install directory
  24. 4) Make sure swigwin install directory is added to PATH env. variable
  25. 5) Make sure env. variables PYTHON_INCLUDE and PYTHON_LIB are set correctly e.g.
  26. PYTHON_INCLUE="c:\Python26\include"
  27. PYTHON_LIB="c:\Python26\libs\python26.lib"
  28. 6) Build python_wolfssl in Release mode only, Debug build fails to find a debug
  29. python library that isn't included by default
  30. 7) The outputs _wolfssl.pyd and wolfssl.py are the wolfssl import library
  31. 8) Can now run python runme.py from the swig directory