If you are using Cygwin GCC to build extension modules, you - must use a Cygwin build of Python. The regular Win32 Python - installation that you can download from python.org will not work with - your compiler because the dynamic linking conventions are - different (you can use MinGW - GCC if you want to build extension modules which are compatible - with a stock Win32 Python). The Cygwin installer may be able to - install an appropriate version of Python, or you can follow the - traditional Unix - installation process to build Python from source. +
If you are using Cygwin GCC to build extension modules, you must use a + Cygwin build of Python. The regular Win32 Python installation that you + can download from python.org will not + work with your compiler because the dynamic linking conventions are + different (you can use MinGW GCC if + you want to build extension modules which are compatible with a stock + Win32 Python). The Cygwin installer may be able to install an appropriate + version of Python, or you can follow the traditional Unix installation + process to build Python from source.
-The special build configuration variables listed above as - "Cygwin only" make it possible to use a regular Win32 - build of bjam to build and test Boost.Python and Boost.Python - extensions using Cygwin GCC and targeting a Cygwin build of Python. - +
The special build configuration variables listed above as "Cygwin + only" make it possible to use a regular Win32 build of bjam to build and + test Boost.Python and Boost.Python extensions using Cygwin GCC and + targeting a Cygwin build of Python.