Changes between Version 12 and Version 13 of Migration From 0.5 Version To 0.6 Version


Ignore:
Timestamp:
Apr 22, 2007 2:50:17 AM (12 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Migration From 0.5 Version To 0.6 Version

    v12 v13  
    11= Migration From 0.5 Version To 0.6 Version = 
    22 
    3 = Changes = 
     3= Summary = 
     4 
     5== Summary of Changes == 
     6  
     7 * Added {{{PJ_POOL_ALLOC_T}}} and {{{PJ_POOL_ZALLOC_T}}} macros in pjlib. 
     8 * Added IP helper API in {{{ip_helper.h}}}. 
     9 * Added new '''PJNATH''' library containing ICE, STUN, and TURN. 
     10 * Most third party libraries now lives in separate directories, under '''third_party''' directory. 
     11 * STUN related settings have been moved from transport config to pjsua config in PJSUA-LIB. 
     12 
     13== Updating the Application == 
     14 
     15=== All Projects === 
     16 
     17 * The STUN settings have been moved from {{{pjsua_transport_config}}} to {{{pjsua_config}}}. 
     18 
     19=== All Visual Studio/Embedded Visual C Projects === 
     20 
     21 * Add '''IPHLPAPI.LIB''' to input library (Visual Studio 6 users see below). 
     22 * Add these third party libraries into your project dependencies: 
     23   * {{{third_party/build/gsm/libgsmcodec}}} 
     24   * {{{third_party/build/ilbc/libilbccodec}}} 
     25   * {{{third_party/build/portaudio/libportaudio}}} 
     26   * {{{third_party/build/resample/libresample}}} 
     27   * {{{third_party/build/speex/libspeex}}} 
     28 
     29=== Visual Studio 6 === 
     30 
     31VS6 users need to download another/newer Platform SDK from MSDN because IPHLPAPI.LIB is not shipped with VS6. This step is not necessasry if VC++ 2005 Express is already installed in the same machine. 
     32 
     33Once Platform SDK has been downloaded, add the relevant include and library paths to VS6 directories, '''after''' the include and library paths of the VS6's Platform SDK. 
     34 
     35=== Makefile based Projects === 
     36 
     37Makefile based project should  
     38 
     39 
     40= Detail Changes = 
    441 
    542== PJLIB == 
     
    3168=== Speex === 
    3269 
    33 Speex now lives in '''{{{third_party/speex}}}''' directory, and is directly synch-ed to main Speex SVN ({{{trunk}}}, although it's locked to a specific revision). This arrangement would make it easy to synchronize !PortAudio with their development. 
     70Speex now lives in '''{{{third_party/speex}}}''' directory, and is directly synch-ed to main Speex SVN ({{{trunk}}}, although it's locked to a specific revision). This arrangement would make it easy to synchronize !PortAudio with Speex development. 
    3471 
    3572The PJMEDIA specific build files for Speex is located under '''{{{third_party/build/speex}}}''' directory. 
     
    5895In addition, PJMEDIA now also supports the sample rate converter in Speex. 
    5996 
    60 To control which resampling back-end to be used in PJMEDIA, declare either of these macros in your {{{config_site.h}}}: 
     97To control which resampling back-end to be used in PJMEDIA, declare either of  
     98 
     99these macros in your {{{config_site.h}}}: 
    61100 * {{{PJMEDIA_HAS_LIBRESAMPLE=1}}}, which is the default. 
    62101 * {{{PJMEDIA_HAS_SPEEX_RESAMPLE=1}}}, if you want to try Speex resampler. 
    63102 
    64103Because of this new arrangements, {{{PJMEDIA_HAS_SMALL_FILTER}}} and {{{PJMEDIA_HAS_LARGE_FILTER}}} macros are now obsolete. 
    65  
    66 '''Changes for (Embedded) Visual Studio Based Projects:''' 
    67  
    68 Visual Studio applications now must link with {{{third_party/lib/libresample-$(TARGET)}}} library, or add '''{{{third_party/build/resample/libresample.dsp}}}''' in the application 's project dependency. 
    69  
    70 '''Changes for Makefile Based Projects:''' 
    71  
    72 There is no change for Makefile based application, as long as it includes PJ's '''{{{build.mak}}}''' file and gets the link specification from that file (as described in [wiki:Getting_Started_Using Getting Started Part II: Building Your Own Application using PJSIP]). 
    73104 
    74105 
     
    85116 
    86117 
     118== PJSUA-LIB == 
    87119 
    88 = Migrating Your Application = 
    89  
    90 == All Applications == 
    91  
    92 If your application is based on PJSUA-LIB, you need to add '''PJNATH''' in your input library, 
    93  
    94 == All Windows and WinCE Applications == 
    95  
    96 What need to change: 
    97  * On Windows and WinCE, the new IP helper abstraction requires application to link with '''IPHLPAPI.LIB'''. Note that IPHLPAPI.LIB is not shipped with Visual Studio 6 so you need to download Platform SDK to get this library. See the section about Visual Studio 6 below. 
    98  
    99  
    100 == Visual Studio 6 == 
    101  
    102 If you're using Visual Studio 6, you need to: 
    103  * download '''Platform SDK''' from MSDN, and  
    104  * add relevant include and library directory to VS6 options, '''after''' the standard Visual Studio 6 include and library path. 
    105  
    106 This is required because Iphlpapi.[h|lib] is not shipped with Visual Studio 6. 
     120The STUN related settings have been moved from transport config to PJSUA config.