cmpscriptlib.html

vxworks相关论文

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
The value of the macro
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpBuildFlagsAdd</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpBuildFlagsAdd</strong> - add flags to the build</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine is just a quick way to append to the build macros
CFLAGS and <b>CFLAGS_AS</b>. It could also be acheived using
cmpBuildMacro[GS]et
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpAdd</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpAdd</strong> - add components to vxWorks</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine adds one or more optional vxWorks components to
the project. For example, one can "cmpAdd <b>INCLUDE_NFS</b>" to add
the NFS client to the vxWorks image.
If a folder is specified (e.g., <b>FOLDER_NETWORK</b>), then all
default components below that folder are added.
The tool will also add any other components needed by the ones
being added, as determined by dependency analysis.
If the global tcl variable cmpInteractive is set to "true", then
the user will be prompted to confirm before the components
and dependencies are added.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>components</b> </td><td align=left> - </td><td align=left> list of components to add  </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="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpRemove</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpRemove</strong> - remove components from vxWorks</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine removes one or more optional vxWorks components from
the project. For example, one can "cmpRemove <b>INCLUDE_NFS</b>" to remove
the NFS client from the vxWorks image.
If a folder is specified (e.g., <b>FOLDER_NETWORK</b>), then all
components below that folder are removed.
The tool will also remove any components that require by the ones
being removed, as determined by dependency analysis.
If the global tcl variable cmpInteractive is set to "true", then
the user will be prompted to confirm before the components
and dependencies are removed.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>components</b> </td><td align=left> - </td><td align=left> list of components to remove  </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="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpListGet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpListGet</strong> - get a list of components in vxWorks</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine returns the list of components in the current vxWorks
project.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
a list of components
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpParamSet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpParamSet</strong> - set a parameter in the current project</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine sets the value of a component parameter. For example,
the component <b>INCLUDE_IOS</b> has parameter <b>MAX_FDS</b> (max # file descriptors
that can be open at once). One can use "cmpParamSet <b>MAX_FDS</b> 60" to
increase the value to 60.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpParamGet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpParamGet</strong> - get a parameter</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine gets the value of a component parameter. For example,
the component <b>INCLUDE_IOS</b> has parameter <b>MAX_FDS</b> (max # file descriptors
that can be open at once). One can use "cmpParamGet <b>MAX_FDS</b>" to
get the current value of that parameter.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
the parameter value, or an empty string if no such parameter exists
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpFileListGet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpFileListGet</strong> - get a list of files in the project</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine returns the list of source files in the project.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
a list of files in the project
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpFileAdd</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpFileAdd</strong> - add a file to the project</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine adds a source file to the project
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>file</b> </td><td align=left> - </td><td align=left> full path to the file being added </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpFileRemove</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpFileRemove</strong> - remove a file from the project</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine removes a source file from the project
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>file</b> </td><td align=left> - </td><td align=left> full path to the file being removed </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpLoad</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpLoad</strong> - dynamically load components</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine dynamically loads one or more components to a
running target. To use this, you must first be connected
to a tgtsvr using wtxToolAttach.
This routine will extract all needed object modules from the
vxWorks archive, and link them together. It will also build the
initialization code needed to initialize the component(s) and
all dependent components. It then loads the modules and the
initialization code, and calls the initialization code.
<p>
Example: To load the vxWorks target shell, do "cmpLoad <b>FOLDER_SHELL</b>"
<p>

</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>cmps</b> </td><td align=left> - </td><td align=left> components to load</tr>
<tr valign=top>
<td align=left><b>mods</b> </td><td align=left> - </td><td align=left> (optional) set of additional object modules to load  </tr>
<tr valign=top>
<td align=left></tr>
</tr>

</table>

<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>, wtxToolAttach

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

</blockquote><h1>autoscale</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>autoscale</strong> - automatically scale vxWorks</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
configure vxWorks components based on what is required by the
project source files. The default is to tell you what scaling can/should
be done, and why. Passing parameter "terse" prints only terse information.
Passing paramter "shrink" causes autoscaling to actually be done.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>arg</b> </td><td align=left> - </td><td align=left> (optional) default is verbose. can also be shrink or terse.  </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="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpUnavailListGet</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpUnavailListGet</strong> - list unavailable components</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine returns a list of components that are known but not
available. A component is not available if it is not installed
in the tree (e.g., an optional product), or it requires an
unavailable component.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
a list of components
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpValidate</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpValidate</strong> - validate the component configuration</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
Check if the current component configuration is valid.
It returns a list of the form {{cmp1 err1} {cmp2 err2} ...}
where cmpX is the name of a misconfigured component, and
errX is an error string describing what is wrong with the
component.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
an error list, or an empty string if the configuration is valid.
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpTest</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpTest</strong> - test the component descriptor files for errors</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine tests the component descriptor files for semantic
errors. For example, it makes sure all components are contained
in exactly one folder. It prints all diagnostic information
to stdout. This routine is a diagnostic tool for component
developers to test that their new components were written
correctly.
It has two optional parameters. <i>components</i> allows one to
restrict the set of components being tested.
<i>buildTest</i> allows one to verify that each component can
be built individually. The most common reason a component
would fail the build test is if the component descriptor
does not have a <b>HDR_FILE</b> containing a prototype for the
components initialization routine.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>components</b> </td><td align=left> - </td><td align=left> (optional) list of components to test (default is all)</tr>
<tr valign=top>
<td align=left><b>buildTest</b> </td><td align=left> - </td><td align=left> (optional) pass any value to see if components can build  </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="./cmpScriptLib.html#top">cmpScriptLib</a></b>

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

</blockquote><h1>cmpInfo</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>cmpInfo</strong> - get info about a set of components</p>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
Print basic information about a component, including the
subtree (other components required by this component), and
supertree (other components that require this component).
The subtree and supertree are computed using the engine's
dependency analyizer.
This routine is primarily used by component authors who
want to check on the scalability of their components.
<p>
</blockquote><h4>PARAMETERS</h4><blockquote><p>
<table>
<tr valign=top>
<td align=left><b>components</b> </td><td align=left> - </td><td align=left> list of components to analyze  </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="./cmpScriptLib.html#top">cmpScriptLib</a></b>

</body>
</html>