Changes between Version 16 and Version 17 of Intel_IPP_Codecs


Ignore:
Timestamp:
Jan 3, 2009 12:04:44 PM (12 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Intel_IPP_Codecs

    v16 v17  
    2828 * Intel IPP library for your platform 
    2929 * Intel IPP samples for your platform 
    30  
    31 We tested with Intel IPP version 5.3. You may be able to use different Intel IPP versions with PJMEDIA, however we have not tested this.  
     30 * Suitable compiler for both PJSIP and IPP for your platform 
     31 
     32 
     33 
     34We tested with Intel IPP '''version 5.3 Update 3''' on both Windows and Linux. You may be able to use different Intel IPP versions with PJMEDIA, however we have not tested this. 
    3235 
    3336{{{ 
     
    3740 
    3841 '''Note that the use of Intel IPP requires a license from Intel, and in addition a license from the parties who own the royalty of the codec(s) may also be required.''' 
     42 
     43{{{ 
     44#!html 
     45</TD></TR></TABLE> 
     46}}} 
     47 
     48[[BR]] 
     49 
     50{{{ 
     51#!html 
     52<TABLE border=0 width="600" bgcolor=#E0E6FF><TR><TD> 
     53}}} 
     54 
     55 '''Update:''' :: 
     56  We have tested Intel IP '''version 6.0 Update 1''' on Windows/Visual Studio and found the following results: 
     57    - the build and integration instructions on this page still apply for version 6.0, with the minor exception that the '''{{{bin}}}''' folder of the {{{speech-codec}}} samples has been renamed to '''{{{_bin}}}'''. 
     58    - there are '''link errors''' when building the application in '''Debug''' mode, something like the following: 
     59      {{{ 
     60msvcrt.lib(ti_inst.obj) : error LNK2005: "private:  
     61  __thiscall type_info::type_info(class type_info const &)" 
     62 (??0type_info@@AAE@ABV0@@Z) already defined in LIBCMTD.lib(typinfo.obj) 
     63 
     64msvcrt.lib(ti_inst.obj) : error LNK2005: "private: class type_info  
     65  & __thiscall type_info::operator=(class type_info const &)"  
     66  (??4type_info@@AAEAAV0@ABV0@@Z) already defined in LIBCMTD.lib(typinfo.obj)'' 
     67      }}} 
     68      We are still unable to resolve this issue. Note that the application builds fine in '''Release''' mode. 
    3969 
    4070{{{ 
     
    6191 1. Go to {{{speech-codecs}}} folder. 
    6292 1. Open the {{{readme.htm}}} file, and follow the instructions there to build the samples from the source. 
    63  
    64 Once the build process done, you should have '''{{{usc.lib}}}''' file somewhere in a directory inside {{{speech-codecs\bin}}} directory (in my case, it's in {{{C:\ipp-samples\speech-codecs\bin\win32_cl9\lib}}} folder). The directory name corresponds to the platform where the samples are built for. 
     93     - Typically the build process will involve just setting the IPPROOT envirunment variable and execute the {{{buildxx.bat}}} batch file. 
     94 
     95Once the build process done, you should have '''{{{usc.lib}}}''' file in a directory inside {{{speech-codecs\bin}}} directory (in my case, it's in {{{C:\ipp-samples\speech-codecs\bin\win32_cl9\lib}}} folder). The directory name corresponds to the platform where the samples are built for. (Note: for IPP version 6, the {{{bin}}} folder has been renamed to {{{_bin}}}). 
    6596 
    6697If you have any problems with installing and/or building the IPP or IPP samples, please read the IPP documentation or contact Intel for support. 
     
    69100 
    70101 1. Add Intel IPP include and library paths to Visual Studio paths. For example if 32bit Intel IPP is installed in {{{C:\Program Files\Intel\IPP\5.3.3.082\ia32}}} directory: 
    71        - add {{{C:\Program Files\Intel\IPP\5.3.3.082\ia32\include}}} to the VS include path 
    72        - add {{{C:\Program Files\Intel\IPP\5.3.3.082\ia32\stublib}}} to the VS library path 
     102       - add to the VS include path: 
     103             - {{{C:\Program Files\Intel\IPP\5.3.3.082\ia32\include}}}  
     104       - add to the VS library path: 
     105             - {{{C:\Program Files\Intel\IPP\5.3.3.082\ia32\lib}}} 
     106             - {{{C:\Program Files\Intel\IPP\5.3.3.082\ia32\stublib}}} 
    73107 1. Add Intel IPP samples include and library path to Visual Studio paths. For example, if Intel IPP samples are located in {{{C:\ipp-samples}}}: 
    74     - add {{{C:\ipp-samples\speech-codecs\core\usc\include}}} to the include path 
    75     - add {{{C:\ipp-samples\speech-codecs\bin\win32_cl9\lib}}} to the library path. Please replace {{{win32_cl9}}} with the actual directory name where the file '''{{{usc.lib}}}''' is found. Please see the IPP build instructions above. 
     108    - add to the include path: 
     109           - {{{C:\ipp-samples\speech-codecs\core\usc\include}}} 
     110    - add to the library path (please replace {{{win32_cl9}}} with the actual directory name where the file '''{{{usc.lib}}}''' is found. Please see the IPP build instructions above): 
     111           - {{{C:\ipp-samples\speech-codecs\bin\win32_cl9\lib}}} 
    76112 
    77113Note that you still need to enable IPP support in your {{{config_site.h}}} in order to use the IPP features. This will be explained in later sections. 
     
    119155=== Enable IPP Support === 
    120156 
    121 By default, IPP support is disabled in PJMEDIA. To enable IPP support, declare the following in your {{{config.site.h}}}: 
     157By default, IPP support is disabled in PJMEDIA. To enable IPP support, declare the following in your {{{config_site.h}}}: 
    122158 
    123159 {{{ 
     
    261297=== Codec Settings === 
    262298 
     299 
    263300Codec settings are managed by setting the appropriate field in {{{settings}}} part of [http://www.pjsip.org/pjmedia/docs/html/structpjmedia__codec__param.htm pjmedia_codec_param] as usual. 
    264301