metaonly module ti.sdo.ce.global.Settings |
 |
Global configuration settings for all Codec Engine packages
This module provides high-level configuration settings for all
Codec Engine packages.
[
more ... ]
var Settings = xdc.useModule('ti.sdo.ce.global.Settings');
module-wide config parameters
DETAILS
This module provides high-level configuration settings for all
Codec Engine packages.
LINKING WITH CODEC ENGINE LIBRARIES
When linking an executable, this module's profile config param is
used to select which libraries are used. See the
profile
config param below. There are three typical use-cases.
1. Link with Codec Engine libraries of a specific profile. Add the
following to your application cfg script.
// set all codec engine libraries to the given profile
xdc.useModule('ti.sdo.ce.global.Settings').profile = "debug";
2. Link with Codec Engine libraries using the program's profile. Add
the following to your application cfg script.
// use the program's profile
var Program = xdc.useModule('xdc.cfg.Program');
xdc.useModule('ti.sdo.ce.global.Settings').profile = Program.build.profile;
3. Specify a profile on a per-package basis.
// specify the profile for some select packages
xdc.loadPackage('ti.sdo.ce').profile = "debug";
xdc.loadPackage('ti.sdo.ce.video').profile = "debug";
xdc.loadPackage('ti.sdo.ce.image').profile = "debug";
xdc.loadPackage('ti.sdo.ce.speech').profile = "debug";
xdc.loadPackage('ti.sdo.ce.audio').profile = "debug";
Note that the third method above does not actually use the profile
config param. It sets the package's profile config param directly.
The default value for the profile config param is release.
Thus, even when building your executable using a debug profile, the
Codec Engine release libraries will be used. This helps to keep the
executable size smaller when you want to debug the application code.
generated on Fri, 24 Feb 2012 03:47:02 GMT