Changes between Version 8 and Version 9 of Intel_IPP_Codecs

Timestamp:

Aug 21, 2008 9:39:50 PM (16 years ago)

Author:

bennylp

Comment:

--

Intel_IPP_Codecs

@@ -66 +66 @@
 
  1. Download Intel IPP and Intel IPP samples from http://www.intel.com/cd/software/products/asmo-na/eng/302910.htm
- 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/'').
- 1. Extract IPP samples to a directory (e.g. to '~/Desktop/ipp-samples').
+ 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/"'').
+ 1. Extract IPP samples to a directory (e.g. to ''"~/Desktop/ipp-samples"'').
 
 
@@ -82 +82 @@
 ==== Running "configure" with IPP support ====
 
+The {{{configure}}} script needs to be invoked with IPP options in order to set up IPP include and library paths.
+
 For 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:
 
@@ -104 +106 @@
 #define PJMEDIA_HAS_INTEL_IPP   1
  }}}
+
+Note that you still need to set this macro even after IPP has been enabled with the {{{configure}}} command.
 
 === Enable/Disable Individual IPP Codec ===
@@ -119 +123 @@
  }}}
 
-=== Linking Options ===
+
+[[BR]]
+
+== Static Linking ==
+
+=== Windows Instructions ===
 
 By 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.
@@ -131 +140 @@
 
 
+=== Linux Instructions ===
+
+By 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:
+
+{{{
+export IPP_LIBS=-lusc -lippsc -lipps -lippsr -lippcore -lguide
+}}}
+
+If 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.
+
+Sample to override the variable in {{{user.mak}}}:
+
+ {{{
+export IPP_LIBS=-lusc -lippscmerged ..
+ }}}
 
 [[BR]]
@@ -152 +176 @@
 [[BR]]
 
+== Setting DLL/Shared Library Path ==
+
+By 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.
+
+=== Setting up DLL Path ===
+
+On Windows, you'd need to add Intel IPP's DLL location to your PATH variable.
+
+=== Setting up LD_LIBRARY_PATH ===
+
+On Linux, you'd need to add Intel IPP shared library location to your {{{LD_LIBRARY_PATH}}} environment variable:
+
+ {{{
+$ export LD_LIBRARY_PATH="$IPPROOT/sharedlib:$LD_LIBRARY_PATH"
+ }}}
+
+
+
+
+[[BR]]
+
 == Open Issues ==
 
@@ -170 +215 @@
 Negotiation 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.
 
-=== Linux Support ===
-
-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.
-
 === MacOS X Support ===