Community
Participate
Working Groups
The xdc.runtime package is _always_ imported during configuration. Why? To generate Rta data: var Rta = xdc.module('xdc.runtime.Rta'); Rta.genRta(prefix + ".rta.xml"); These statements should probably be bracketed by: if ("xdc.runtime" in xdc.om) { } as is done in other parts of xdc.cfg. Executables that don't require the xdc.runtime shouldn't have a dependency on it.
The package xdc.runtime ended up in 3.16 configurations in two ways. First, the app was not setting rtsName to 'null', and second, the call to xdc.runtime.finalize() in xdc.cfg.Main.xs wasn't checking if xdc.runtime is loaded in the configuration at all. The second problem was fixed in 3.20 in xdc-v20, rev. 882 in svn, and now it's applied in xdc-u18 for 3.16.04. The first problem is a user's error.
Built a BIOS5 application using XDCtools 3.16.03.36. Command line build was used using the 'xdc' tool.The 'rtsName' field of 'Executable.Attrs' is set to null in the 'package.bld' script. The 'package.ext.xml' file of the released package had a reference to 'xdc.runtime'. Rebuilt application using XDCtools 3.16.04.38-eng. There was no reference to 'xdc.runtime' in 'package.ext.xml'.
Verified with XDCtools 3.16.04.38-eng
3.20.02 and 3.16.05 are available here:http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/
