On Sun, Feb 17, 2013 at 9:27 AM, Xiaofan Chen <[email protected]> wrote: > Here is my run log. > > 1. Start MSys and prepare > $ cd /c/work/ > $ cd libftdi/libftdi1-1.0 > $ mkdir build_python32 > $ cd build_python32/ > > 2. Using CMake-GUI > $ cmake-gui > > 2.1) Select Configure and choose "MSys Makefile". It will > generate some red errors with regard to libusb-1.0. > > 2.2) Point CMake to find the correct location of your swig.exe > location. In my case, it is here. > C:/Program Files/swigwin-2.0.9/swig.exe > > Point CMake to find the correct libusb-1.0 (using libusbx > 1.0.14 Windows binary) include file (libusb.h) and library file > (libusb-1.0.dll.a). > > In my case, libusb.h is here. > C:/work/libusbx/libusbx-1.0.14-win/include/libusbx-1.0 > libusb-1.0.dll.a is here. > C:/work/libusbx/libusbx-1.0.14-win/MinGW32/dll/libusb-1.0.dll.a > > Ignore the other issues like Boost bindings. > > 2.3) Point CMake to the correct Python locations if it has > not done so (when you have multiple Python installations > like me). > Python executable: C:/Python32/python.exe > Python include dir: C:/Python32/include > Python library: C:/Python32/libs/libpython32.a > > 2.4) Configure again, you should now see no more red errors. > 2.5) Click "Generate" to generate the Makefile. > 2.6) Close CMake-GUI > > 3. Run make to generate the binaries. > $ make > > 4. Copy libusb-1.0.dll and libftdi1.dll to the Python directory > C:\Python32 > > 5. Copy the python binding files _ftdi1.pyd and ftdi1.py > to Python library site package dirctrory > C:\Python32\Lib\site-packages > > 6. Start Python 3.2 and run some tests.
Hopefully you can follow the steps and build your own Python bindings. If not, I have uploaded another updated package to include Boost binding and Python 2.7/3.2/3.3 bindings and you can test the new devkit package. -- Xiaofan -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
