For example, a package's build script might build an executable for each possible level of a "trace" value:

              for (t = 0; t < NUM_TRACE_LEVELS; t++) {
                      :
                  Pkg.addExecutable("myExe" + t, targ, plat, {
                      cfgArgs:   "{traceLevel: " + t + "}",
                      cfgScript: "myExe.cfg"
                  });
              }

In this case, the configuration script myExe.cfg can reference the "trace level" set in the build script by referencing the Program.build.cfgArgs object directly:

              if (Program.build.cfgArgs.traceLevel == 1) {
                  :
              }

If this parameter is not specified, the package containing the configuration script is used as the home package. This ensures that the results of a configuration script are independent of the package building the configuration. In most cases, the build package is the package containing the configuration script and this distinction is not important. But there are times when it is important to control the home package; e.g., when an external tool generates a configuration script from information supplied by another package or when a configuration script in not in any package.

If this string is set to a non-null value, and does not have an extension, then the extension ".cfg" is automatically added.

If the specified configuration file does not exist in the package where the executable is being built and the name does not begin with "./", it is searched for along the package path. Thus, it is possible to use configuration scripts in other packages to build executables; e.g., to use the configuration script "myExe.cfg" from a ti.bios.examples.hello package, cfgScript should be set to "ti/bios/examples/hello/myExe.cfg".

The package containing the specified configuration script is imported prior to running the configuration script and this package is used to set xdc.$homepkg; thus, configuration scripts that use xdc.$homepkg will configure the same executable independent of the package building the executable.

If this field is not set or set to null, the value of xdc.bld.PackageContents.attrs.profile is used. If xdc.bld.PackageContents.attrs.profile is not specified or equal to null, the "release" profile is used.

This package is implicitly loaded prior to running the executable's configuration script. If this field is set to null, no package will be pre-loaded. If this field is not set (or set to undefined), the package specified by this executable's target will be used (see xdc.bld.ITarget.rts) .

As with configuration scripts, if the specified file does not exist in the package where the executable is being built and the name does not begin with "./", it is searched for along the package path. Thus, it is possible to use templates in other packages to build executables; e.g., to use the linker command file "myExe.cmd" from the ti.bios.examples.hello package, linkTemplate should be set to "ti/bios/examples/hello/myExe.cmd".

      Pkg.attrs.profile = 'release';
      var exe = Pkg.addExecutable('example', ..., {profile: 'debug'});

      <name>.x<target_suffix>

      #include <xdc/std.h>
      #include <ti/bios/include/log.h>

      #include <xdc/cfg/global.h>    // include declaration of trace
      
      int main(int argc, char *argv[])
      {
          LOG_printf(trace, "hello world");
              :
      }

          myExe.addObjects(["hello"]);

          myExe.addObjects(["hello.c"]);

          myExe.addObjects(["foo/hello.c"]);

          myExe.addObjects(["fir.c", "iir.c"], {defs: "-D_DEBUG"});