Tornado

Tornado 2.0
User’s Guide
about components that may not be required for your application. To automatically
scale VxWorks, select Auto Scale from the context menu in the VxWorks view of the
workspace window to display the Auto Scale dialog box, and click OK.
NOTE: The auto scale feature detects only statically calculable dependencies
between the application code and VxWorks. Some components may be needed
even if they are not called by your application. This is especially true for servers
such as WDB, NFS, and so on.
4.4.2 Adding Application Initialization Routines
When VxWorks boots, it initializes operating system components (as needed), and
then passes control to the user’s application for initialization. To add application
initialization calls to VxWorks, double-click on userAppInit.c to open the file for
editing, and add the call(s) to usrAppInit( ). Figure 4-33, for example, illustrates the
addition of a call to runItAll( ), the main routine in the application file
helloWorld.c.
4.5 Working With Build Specifications
The project facility allows you to create, modify, and select specifications for any
number of builds. A default build specification is defined when you create your
project. While a BSP is usually designed for one CPU, you can create build
specifications for different image types and optimization levels, specifications for
builds that include debugging information and builds that don’t, and so on.
4.5.1 Changing a Build Specification
Each build specification consists of a set of options that define the VxWorks image
type (for VxWorks and bootable application projects), makefile rules, macros, as
well as compiler, assembler, and linker options.
128