/*
 *  Copyright 2002 by Texas Instruments Incorporated.
 *  All rights reserved. Property of Texas Instruments Incorporated.
 *  Restricted rights to use, duplicate or disclose this code are
 *  granted through contract.
 *  
 */
/* "@(#) ReferenceFrameworks 1.20.10 10-25-02 (swat-c15)" */
/*
 *  Linker-command file for the RF5 application
 *
 *  This file governs the linking process. The minimum of information
 *  it needs to contain is:
 *
 *  1) the list of libraries used by the application; they will be
 *     searched for in directories specified in the "build options->
 *     linker->library search path" field of the project
 *  2) inclusion of the configuration file automatically generated
 *     by the CDB that handles BIOS objects
 *  
 *  In addition, it may define symbols used by the application 
 *  (typical for XDAIS algorithms, an ALG algorithm provided by
 *  vendor VEN has its function table named as ALG_VEN_IALG,
 *  but the application may always refer to it as ALG_IALG,
 *  if there is an assignment _ALG_IALG = _ALG_VEN_IALG in this file.
 *  Binding to a specific implementation of an algorithm then occurs
 *  in the linker-command file. Therefore, if another version of 
 *  algorithm ALG is supplied by vendor VEN2, it only takes to change
 *  the assignment in this file to _ALG_IALG = _ALG_VEN2_IALG
 *  and relink the object files without having to recompile the application.
 *
 *  Finally, it may employ some space optimization techniques, such as
 *  moving all initialization code to external memory or even overlaying
 *  initialization code with data.
 */

-l h263_loopbackcfg.cmd
_H263ENC_IH263ENC =   _H263ENC_TI_IH263ENC;
_H263DEC_IH263DEC =   _H263DEC_TI_IH263DEC;


SECTIONS
{
        
    H263ENC:            > SDRAM, align=0x1000
    { 
		*(h263encp)
        *(h263enc)
        *(h263share)
		*(h263decp)
        *(h263dec)
    }
}

-l vport.l64
-l algrf.l64
-l chan.l64
-l icc.l64
-l scom.l64
-l sscr.l64
-l utl.l64
-l C:\ti\boards\evmdm642\lib\evmdm642bsl.lib
-l h263enc.l64
-l h263dec.l64