2.1  UNIX Hosts

For information on how to install the WindNet STREAMS for Tornado Component Release CD-ROM, as well as other Wind River Systems products, refer to the Wind River Products Installation Guide, Tornado 1.0, Edition 3 or later. Installation keys, used to specify the components to be installed, are printed on the CD-ROM sleeve. For a general discussion on configuring the entire Tornado cross-development environment, see the Tornado User's Guide: Getting Started.


*   

WARNING: Including WindNet STREAMS in VxWorks may cause the loading of the VxWorks system image to fail. This failure is due to the static maximum size of the VxWorks image. This problem can be fixed by either reducing the size of the VxWorks image (by removing unneeded options), or by burning new boot ROMs. For more information about this problem, see the WindNet STREAMS for Tornado Component Release Notes: Known Problems.

The installation process updates the appropriate VxWorks target libraries with the new object modules, installs source and include file changes into the VxWorks tree, and creates archive subdirectories, named ARCHIVE.streams-1.0, in each directory where files are being updated. For example, in the header file directory, it creates h/ARCHIVE.streams-1.0 (the suffix .streams-1.0 identifies files saved as part of the WindNet STREAMS installation). Older versions of the files are placed in the ARCHIVE.streams-1.0 subdirectory. You can remove the ARCHIVE.streams-1.0 subdirectories in your VxWorks tree once you are certain you have integrated any changes you may have made to them in the STREAMS versions of these files.

Once the WindNet STREAMS modules have been installed, you must remake VxWorks. To do this, go to your BSP directory and remake your VxWorks system image. Be sure that you have defined the appropriate constants (listed in §6. Configuration) in configAll.h to include all desired modules. For information about configuring and rebuilding VxWorks, see the VxWorks Programmer's Guide, 5.3: Configuration.

In addition, you may need to recompile any applications code that includes the modified header files.