Texas Instruments Codec Engine Server Delivering a Codec Server, Editing the Linker Command File

Models: Codec Engine Server

1 36
Download 36 pages 9.54 Kb
Page 32
Image 32
2.2.6Editing the Linker Command File

Delivering a Codec Server

Change the bold text in the following line to match your server name:

var serverName = "my_server";

When you have finished development, you may want to change "debug" in the following line to "release":

Pkg.attrs.profile = "release";

Do not edit package.mak, any files that begin with a period, or anything in the "package" directory. These files are generated when you build. Any modifications to these files are overwritten whenever you rebuild.

2.2.6Editing the Linker Command File

If you want to specify any other DSP linker commands, add those commands to the link.cmd linker command file.

2.2.7Editing the main.c File

You may add to the main.c source file as necessary. Since DSP/BIOS runs its threads after main() completes, you should only put initialization statements in main(), and main() must run to completion rather than looping.

2.2.8Editing the makefile

The makefile should not require changes. However, you may need to add repositories to the XDC_PATH used in the makefile by modifying the xdcpaths.mak file.

2.3Delivering a Codec Server

To distribute a Codec Server, you should deliver the package used to produce the server, including the server executable. The package contains the configuration scripts that produced the server. The package information also specifies the version of the compiler used to make the server and the versions of the codecs used to make the server.

When you distribute a Codec Server, you should provide documentation that includes the following information:

Codec Server name

Build options used for compiling and linking

List of the algorithms available in the Codec Server

2-16

Page 32
Image 32
Texas Instruments Codec Engine Server Delivering a Codec Server, Editing the Linker Command File, Editing the main.c File