Changes between Version 8 and Version 9 of Intel_IPP_Codecs


Ignore:
Timestamp:
Aug 21, 2008 9:39:50 PM (11 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Intel_IPP_Codecs

    v8 v9  
    6666 
    6767 1. Download Intel IPP and Intel IPP samples from http://www.intel.com/cd/software/products/asmo-na/eng/302910.htm 
    68  1. Extract the archive to a temporary folder and run the installer (e.g. ''./install.sh''). The default installation options will install it to ''/opt/intel/ipp/'' directory (e.g. ''/opt/intel/ipp/5.3.1.062/ia32/''). 
    69  1. Extract IPP samples to a directory (e.g. to '~/Desktop/ipp-samples'). 
     68 1. Extract the archive to a temporary folder and run the installer (e.g. ''./install.sh''). The default installation options will install it to ''"/opt/intel/ipp/"'' directory (e.g. ''"/opt/intel/ipp/5.3.1.062/ia32/"''). 
     69 1. Extract IPP samples to a directory (e.g. to ''"~/Desktop/ipp-samples"''). 
    7070 
    7171 
     
    8282==== Running "configure" with IPP support ==== 
    8383 
     84The {{{configure}}} script needs to be invoked with IPP options in order to set up IPP include and library paths. 
     85 
    8486For this tutorial, we'll use two environment variables to hold the location of IPP and IPP samples. Sample ''bash'' session to run the {{{configure}}} script: 
    8587 
     
    104106#define PJMEDIA_HAS_INTEL_IPP   1 
    105107 }}} 
     108 
     109Note that you still need to set this macro even after IPP has been enabled with the {{{configure}}} command. 
    106110 
    107111=== Enable/Disable Individual IPP Codec === 
     
    119123 }}} 
    120124 
    121 === Linking Options === 
     125 
     126[[BR]] 
     127 
     128== Static Linking == 
     129 
     130=== Windows Instructions === 
    122131 
    123132By default, PJMEDIA will automatically link with Intel IPP libraries when Visual Studio is used. This is done by using using {{{#pragma comment(lib)}}} constructs in the source code. This is convenient, however it will only link with the stub libraries and the Intel IPP DLL's will be required when distributing the application. 
     
    131140 
    132141 
     142=== Linux Instructions === 
     143 
     144By default, the configuration and build system will link with Intel IPP shared libraries. This is controlled by the {{{IPP_LIBS}}} setting in the auto-generated {{{build.mak}}} file: 
     145 
     146{{{ 
     147export IPP_LIBS=-lusc -lippsc -lipps -lippsr -lippcore -lguide 
     148}}} 
     149 
     150If you want to configure static linking, you can override this variable in your {{{user.mak}}} file, or change the value in the {{{build.mak}}}. The later is not recommended since the {{{build.mak}}} file will be overwritten everytime {{{configure}}} is run. 
     151 
     152Sample to override the variable in {{{user.mak}}}: 
     153 
     154 {{{ 
     155export IPP_LIBS=-lusc -lippscmerged .. 
     156 }}} 
    133157 
    134158[[BR]] 
     
    152176[[BR]] 
    153177 
     178== Setting DLL/Shared Library Path == 
     179 
     180By default, the build process links with the IPP dynamic libraries. Because of this, you'd need to set the DLL/shared library path before running PJSIP application that links with Intel IPP. 
     181 
     182=== Setting up DLL Path === 
     183 
     184On Windows, you'd need to add Intel IPP's DLL location to your PATH variable. 
     185 
     186=== Setting up LD_LIBRARY_PATH === 
     187 
     188On Linux, you'd need to add Intel IPP shared library location to your {{{LD_LIBRARY_PATH}}} environment variable: 
     189 
     190 {{{ 
     191$ export LD_LIBRARY_PATH="$IPPROOT/sharedlib:$LD_LIBRARY_PATH" 
     192 }}} 
     193 
     194 
     195 
     196 
     197[[BR]] 
     198 
    154199== Open Issues == 
    155200 
     
    170215Negotiation of various AMR options in SDP is currently not supported. The AMR mode is locked to bandwidth-optimized, and when AMR with octet-aligned packet is received, the behavior is undefined. 
    171216 
    172 === Linux Support === 
    173  
    174 Currently IPP integration is not supported by the autoconf script. You must add the appropriate CFLAGS and LDFLAGS in {{{user.mak}}} file in order to use IPP. 
    175  
    176217=== MacOS X Support === 
    177218