Since VXLIB is a collection of individual kernels, any combination of the kernels that comprise VXLIB may be integrated into a system individually. Integration, for single or multiple kernels, requires simple steps below:

The sections that follow provide details regarding the above steps.

Compile VXLIB

On installation, the VXLIB optimized library is built and ready to link. Therefore, this step is only required when the original kernel source code has been refined, standalong applications need to built, or contributions have been added. See VXLIB Build Process for details regarding building VXLIB.

Add VXLIB API Calls

Add calls to VXLIB kernels within the system source code as necessary. Any system source file that contains calls to an VXLIB kernel will require that the VXLIB header file vxlib.h is included. See the VXLIB Function Reference for details on individual kernel APIs.

System Compilation

Include Paths

To compile the system code with VXLIB integrated, the following two paths should be added to the compiler's include path search list:

The path to vxlib.h : <VXLIB root>\packages\ti\vxlib directory
The path to the <VXLIB root>\packages directory.

These paths will depend on the VXLIB root installation directory. This allows the main VXLIB header file to be moved from within the installation directory and still recognize the individual kernel headers.

Preprocessor Defines

(Optional) When compiling the final executable as a PC target (X86 or x86_64), the following preprocessor definitions should be added to the compiler's preprocessor defines list:

_HOST_BUILD
_TMS320C6600
TMS320C66X
CORE_DSP
HOST_EMULATION

Linking VXLIB

The path to the VXLIB required libraries must be provided to the linker.

Note: When compiling for PC target (X86 or x86_64), the common library also needs to be linked along with the vxlib library due to dependencies on emulated intrinsic that are part of the common library.