datadoclib.html

vxworks相关论文

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
the list of components and subfolders of the given folder
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

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

</blockquote><h1>cxrSizeGet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cxrSizeGet</strong> - get the size of a set of components</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine returns the appoximate size of the smallest kernel
that contains the given set of components.
The size is always an underestimate, because it only takes into account
the size of the .o's in the vxWorks archive - and not the size
of the BSP and configuration files.
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> DataDoc corresponding the the vxWorks archive  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
three sizes; text, data, and bss
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>, mxrDataDocCreate

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

</blockquote><h1>modAnalyze</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>modAnalyze</strong> - analyze archives and/or object modules</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
Create an MxrDoc corresponding to a set of object modules and archives.
This routine is just like mxrDataDocCreate, but the toolchain
parameter does not require a "tc_" prepended.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>fileList</b> </td><td align=left> - </td><td align=left> list of object moduless and archives to analyze</tr>
<tr valign=top>
<td align=left><b>toolchain</b> </td><td align=left> - </td><td align=left> toolchain used to build the objects (e.g., PPC604gnu)  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

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

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

</blockquote><h1>modTrace</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>modTrace</strong> - trace module dependencies</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
Given two object modules within an archive, find the shortest path
between them. The result is printed to stdout in the form
"fromMod mod1 mod2 ... toMod". In verbose mode it also prints
the reason for the dependencies by inserting a list of symbols
between each module dependecy. That way you can find out what
symbols caused the dependencies between, for example, mod1 and
mod2.
<p>
This routine can be useful when tracking scalability bugs.
For example, if you look at the output of "modSubtree" on
a given object module, and find it contains many more module
dependencies than you expected, then this routine can show
you why those dependencies occured.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>modDataDoc</b> </td><td align=left> - </td><td align=left> MxrDoc handle returned from modAnalyze</tr>
<tr valign=top>
<td align=left><b>fromMod</b> </td><td align=left> - </td><td align=left> module to trace from</tr>
<tr valign=top>
<td align=left><b>toMod</b> </td><td align=left> - </td><td align=left> module to trace to</tr>
<tr valign=top>
<td align=left><b>verbose</b> </td><td align=left> - </td><td align=left> (optional) set to verbose to print sym info  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<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="modSubtree"></a>
<p align=right>
<a href="rtnIndex.html"><i>Project Database Library :  Tcl Procedures</i></a></p>

</blockquote><h1>modSubtree</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>modSubtree</strong> - find (recursivley) all modules called by a set of modules</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine is a recusive version of modCalls. It lets you know what
modules are required by a given set of modules.
Suppose module1 calls module2, and module2 calls module3.
Then the subtree of module1 would contain both module2 and module3.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>modDataDoc</b> </td><td align=left> - </td><td align=left> return value of modAnalyze</tr>
<tr valign=top>
<td align=left><b>mods</b> </td><td align=left> - </td><td align=left> list of module  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
list of modules called by mods (recursive)
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

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

</blockquote><h1>modSupertree</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>modSupertree</strong> - find (recursivley) all modules that call a set of modules</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine is a recusive version of modCalledBy. It lets you know what
modules require a given set of modules.
Suppose module1 calls module2, and module2 calls module3.
Then the supertree of module3 would contain both module2 and module1.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>modDataDoc</b> </td><td align=left> - </td><td align=left> return value of modAnalyze</tr>
<tr valign=top>
<td align=left><b>mods</b> </td><td align=left> - </td><td align=left> list of module  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
list of modules that call mods (recursive)
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

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

</blockquote><h1>modCalledBy</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>modCalledBy</strong> - find all modules that call a given set of modules</p>

</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>modDataDoc</b> </td><td align=left> - </td><td align=left> return value of modAnalyze</tr>
<tr valign=top>
<td align=left><b>mods</b> </td><td align=left> - </td><td align=left> list of module  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
list of modules that call mods
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

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

</blockquote><h1>modCalls</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>modCalls</strong> - find all modules that are called by a given set of modules</p>

</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>modDataDoc</b> </td><td align=left> - </td><td align=left> return value of modAnalyze</tr>
<tr valign=top>
<td align=left><b>mods</b> </td><td align=left> - </td><td align=left> list of module  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
list of modules that mod calls
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

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

</blockquote><h1>modInfo</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>modInfo</strong> - get info about module relationships</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine can be used to get any other information
associated with a set of modules, according to the MxrDoc schema.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>modDataDoc</b> </td><td align=left> - </td><td align=left> return value of modAnalyze</tr>
<tr valign=top>
<td align=left><b>mods</b> </td><td align=left> - </td><td align=left> list of module (typically just one)</tr>
<tr valign=top>
<td align=left><b>info</b> </td><td align=left> - </td><td align=left> info to get (e.g., exports, imports, declares, textSize, ...)  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
list of modules that mod calls
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./dataDocLib.html#top">dataDocLib</a></b>

</body>
</html>