To configure WindNet STREAMS into your VxWorks target, follow these steps:

1. Define configuration constants in configAll.h that suit your application needs. WindNet STREAMS is designed to offer you scalable functionality.

1. To include all services, define INCLUDE_STREAMS_ALL in configAll.h. By default, this constant is located in the EXCLUDED FACILITIES section. Move it to the INCLUDED FACILITIES section.

2. To include only basic STREAMS services, define INCLUDE_STREAMS in configAll.h. You can then include any of the other facilities provided with WindNet STREAMS by defining in configAll.h their respective configuration constants, as listed in Table 8. Each of these constants is described briefly in the sections that follow. By default, these constants are located in the EXCLUDED FACILITIES section of configAll.h. To make them operational, move the desired constants to the INCLUDED FACILITIES section.

1. Modify the constants shown in Table 9, all located in configAll.h, if their default values do not agree with your application requirements. These constants control the operation of WindNet STREAMS and each is described in one of the subsections in §6.2 WindNet STREAMS Configuration.

1. Rebuild VxWorks.

   Table 8.   WindNet STREAMS Configuration Constants

   Constant	Facility Included
   INCLUDE_STREAMS	Basic STREAMS services.
   INCLUDE_STREAMS_ALL	All the STREAMS services in this table.
   INCLUDE_STREAMS_SOCKET	Socket library and module.
   INCLUDE_STREAMS_TLI	XTI/TLI library and module.
   INCLUDE_STREAMS_DLPI	DLPI driver.
   INCLUDE_STREAMS_AUTOPUSH	Autopush utility.
   INCLUDE_STREAMS_STRACE	Strace utility.
   INCLUDE_STREAMS_STRERR	Strerr utility.
   INCLUDE_STREAMS_DEBUG	Show routines.

This constant forces the inclusion of all STREAMS services supported by WindNet STREAMS and listed in Table 8, except INCLUDE_STREAMS_DEBUG which should be defined only during debugging.

The constant INCLUDE_STREAMS provides basic WindNet STREAMS services, that is, protocol services to protocol drivers and modules. The user application interface to access STREAMS-based protocols is included as part of this option. The STREAMS log and nuls drivers are included, as well as the pipemod module.

This option adds the show routines available with WindNet STREAMS useful for debugging STREAMS applications. These routines display the STREAMS queues, messages in the queues, STREAMS statistics, and STREAMS module and driver information. For a list and description of each of these routines, call or see the manual entry for strmShow( ). For information on how to use the debug printing option, see §5.1 cmn_err( ): STREAMS Debug Printing.

This constant adds the strace utility, which works in conjunction with the WindNet STREAMS log driver to display or store trace messages from a STREAMS module or driver. This utility can be very useful when debugging STREAMS modules and drivers. The #define STREAMS_STRACE_OUTPUT can be set to a directory in the host machine where trace messages can be stored (see §6.2.8 STREAMS_STRACE_OUTPUT_DIR). For information on how to use the strace utility, see §5.2.1 strace Utility.

This constant adds the strerr utility which works in conjunction with the WindNet STREAMS log driver to store in a file error messages coming from STREAMS drivers and modules. The file is created in the directory specified with the #define STREAMS_STRERR_OUTPUT (see also §6.2.7 STREAMS_STRERR_OUTPUT_DIR). This directory must be accessible to the VxWorks target. For information on how to use the strerr utility, see §5.2.2 strerr Utility.

This option adds the autopush utility which works in conjunction with the STREAMS SAD driver. Use the autopush utility to configure the SAD driver to automatically push modules on top of a STREAMS driver when the driver is opened by an application. For more information on using autopush and the SAD driver, see §3.4.1 The Autopush Utility.

This option adds to the WindNet STREAMS package a STREAMS socket library and the STREAMS driver sockmod. The socket library can then be used to access STREAMS transport providers. For information on using STREAMS sockets, see §3.2 STREAMS Sockets Programming.

This option adds to the WindNet STREAMS package a STREAMS Transport Library Interface (TLI), and the STREAMS modules tirdwr and timod. The TLI library can then be used to access STREAMS transport providers which are compatible with TPI. For information on the XTI and TLI interfaces, see §3.1 XTI/TLI Programming.

This facility adds to the WindNet STREAMS package a Data Link Provider Interface (DLPI) driver, /dev/dlb, that can be used to access existing VxWorks Ethernet drivers. The DLPI driver is provided to allow backward compatibility to previously released VxWorks Ethernet drivers. The capabilities of this driver are limited; see §3.3 Data Link Provider Interface (DLPI) Driver for more information.