datadoclib.html

vxworks相关论文

<td align=left><b>toolchain</b> </td><td align=left> - </td><td align=left> toolchain of the form ::tc_<i>CPUTOOL</i></tr>
<tr valign=top>
<td align=left><b>fileList</b> </td><td align=left> - </td><td align=left> list of object files and archives  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
an MxrDoc
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>, <b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>, cmpProjHandleGet

<hr>
<a name="mxrTcGet"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>mxrTcGet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>mxrTcGet</strong> - get the toolchain associated with an MxrDoc</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine only works on MxrDoc's created by mxrDataDocCreate.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>mxrDoc</b> </td><td align=left> - </td><td align=left> MxrDoc  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
toolchain associated with this MxrDoc
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

<hr>
<a name="mxrSupertree"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>mxrSupertree</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>mxrSupertree</strong> - recursively, what modules call a given set of modules</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
Suppose module1 calls module2, and module2 calls module3.
Then the supertree of module3 would contain both module2 and module1.
This routine is just like modSupertree, but taks a DataSet as input
instead of a list of module names.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>modSet</b> </td><td align=left> - </td><td align=left> DataSet of modules  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
list of modules in the supertree of the input set
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

<hr>
<a name="mxrSubtree"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>mxrSubtree</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>mxrSubtree</strong> - recursively, what modules are called by a given set of modules</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
Suppose module1 calls module2, and module2 calls module3.
Then the subtree of module1 would contain both module2 and module3.
This routine is just like modSubtree, but taks a DataSet as input
instead of a list of module names.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>modSet</b> </td><td align=left> - </td><td align=left> DataSet of modules  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
list of modules in the subtree of the input set
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

<hr>
<a name="mxrSizeGet"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>mxrSizeGet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>mxrSizeGet</strong> - return the size of a set of modules</p>

</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>modSet</b> </td><td align=left> - </td><td align=left> DataSet of modules  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
a list of three elements: text, data, bss sizes.
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

<hr>
<a name="mxrDocValidate"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>mxrDocValidate</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>mxrDocValidate</strong> - test for duplicate symbol names and other bugs</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine checks for bugs in an MxrDoc, and prints any errors
found to stdout. The only errors currently tested for are
symbols exported by more than one module.
<p>
</blockquote><h4>PARAMTERS</h4><blockquote><p>
mxrDoc : MxrDoc to test
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

<hr>
<a name="cxrDataDocCreate"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>cxrDataDocCreate</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cxrDataDocCreate</strong> - create a component xref document from .cdf files</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine takes a path to look for .cdf files, and returns
a the corresponding CxrDoc. A toolchain must be specified of the
form ::tc_<i>CPUTOOL</i> (e.g., ::tc_PPC604gnu). Before importing the
.cdf files into a CxrDoc, the toolchain's preprocessor
is run on the .cdf files with -DCPU=<i>CPU</i>. This allows CPU-specific
overrides of the component descriptors to be made in the .cdf files.
<p>
Note: If you source <b>cmpScriptLib.tcl</b>, you can call "cxrDocCreate $hProj"
to get the CxrDoc associated with a given project handle.
cxrDocCreate is actually built on top of cxrDataDocCreate.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>cdfPath</b> </td><td align=left> - </td><td align=left> path to search for .cdf files</tr>
<tr valign=top>
<td align=left><b>toolchain</b> </td><td align=left> - </td><td align=left> toolchain of the form ::tc_<i>CPUTOOL</i>  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
a CxrDoc
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>, <b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>, cmpProjHandleGet

<hr>
<a name="cxrSupertree"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>cxrSupertree</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cxrSupertree</strong> - what components require a given set of components</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
If a user wants to exclude a set of components, this routine
can be used to tell what other components also need to be
excluded by dependency.
Because component dependencies are built on top of module
dependencies, this routine also requires an MxrDoc containing
information about the component's modules.
The config engine uses this routine with parameter <i>mxrDoc</i> as
the return value of "mxrDocCreate $hProj".
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>cmpSet</b> </td><td align=left> - </td><td align=left> DataSet of components</tr>
<tr valign=top>
<td align=left><b>mxrDoc</b> </td><td align=left> - </td><td align=left> MxrDoc  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
the list of all components that require components in cmpSet
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>, mxrDataDocCreate

<hr>
<a name="cxrSubtree"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>cxrSubtree</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cxrSubtree</strong> - what components are required by a given set of components</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
If a user wants to include a set of components, this routine
can be used to tell what other components also need to be
included by dependecy.
Because component dependencies are built on top of module
dependencies, this routine also requires an MxrDoc containing
information about the component's modules.
The config engine uses this routine with parameter <i>mxrDoc</i> as
the return value of "mxrDocCreate $hProj".
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>cmpSet</b> </td><td align=left> - </td><td align=left> DataSet of components</tr>
<tr valign=top>
<td align=left><b>mxrDoc</b> </td><td align=left> - </td><td align=left> MxrDoc  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
the list of all components that are required by components in cmpSet
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>, mxrDataDocCreate

<hr>
<a name="cxrSubfolders"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>cxrSubfolders</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cxrSubfolders</strong> - find everything under a given folder recursivly</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
Components are grouped into folders. This routine returns the
set of componenents and folders (recursively) under a given folder.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>cmpSet</b> </td><td align=left> - </td><td align=left> DataSet of component Folder objects.  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>