Changes between Version 10 and Version 11 of Python_SIP/Build_Install

Timestamp:

Jul 24, 2008 1:11:06 PM (16 years ago)

Author:

bennylp

Comment:

--

Python_SIP/Build_Install

@@ -15 +15 @@
 ==== Requirements ====
 
+ 1. The [http://www.pjsip.org/using.htm#gnu_req usual requirements to build PJSIP], e.g. {{{make}}}, {{{gcc}}}, and {{{binutils}}}.
  1. '''Python''': this normally should have been installed on every Linux.
  1. '''Python development package''', to build the C extension. This might be called {{{python-devel}}} (e.g. on Fedora) or {{{python2.4-dev}}} or {{{python2.5-dev}}} (e.g. on Ubuntu).
@@ -35 +36 @@
  }}}
 
-=== Microsoft Windows ===
+=== Microsoft Windows with Visual Studio ===
 
 ==== Requirements ====
 
+ 1. The usual [http://www.pjsip.org/using.htm#vs_req PJSIP requirements for Windows], e.g. Visual Studio along with Platform SDK and DirectX SDK.
  1. '''Python SDK''': I personally use [ftp://ftp.activestate.com/ActivePython/windows/2.4/ ActivePython-2.4.3-12] distribution from [http://www.activestate.com ActiveState], since it has a matching debug package.
- 1. '''Visual Studio''': for building the C extension.
  1. '''Optional: debug package''': the debug package is useful if you want to debug the C extension. You can download it from ftp://ftp.activestate.com/ActivePython/etc/
 
-==== Building the Module with Visual Studio ====
+==== Building the Modules ====
 
 '''Step 1: Building the C Extension''':
@@ -64 +65 @@
  }}}
 
-==== Building the Module with MinGW ====
+=== Microsoft Windows with MinGW ===
 
-Adamczak Krzysztof suggested this on PJSIP mailing list to build the extensions with MinGW:
+I did not try this myself since I use Visual Studio, but Adamczak Krzysztof suggested this on PJSIP mailing list to build the extensions with MinGW:
 
  {{{
   python setup.py build_ext --compiler=mingw32 install
  }}}
+