3.3 Using the buildserver and buildclient Commands

Both the buildclient and buildserver commands are available to Windows Server systems; however, only the buildclient command is available to Windows desktop systems, meaning that only Tuxedo application clients can be built on a Windows desktop system. For more information about the build commands, see buildclient(1)and buildserver(1)in Oracle Tuxedo Command Reference.

There are differences between how the options to the buildclient and buildserver commands work on non-integrated development environments and on integrated development environments, as indicated in the following table.

Table 3-1 Using the buildserver and buildclient Commands

To . . .	In a Non-Integrated Development Environment,Use This Option . . .	In an Integrated Development Environment . . .
Turn on verbose mode	-v	All options are displayed on tabs by default. (The -v option is unnecessary and unsupported.)
Specify an output file	-o (output_filename)	Select Settings from the msdev Build menu. Select the Link tab in the Project Settings dialog box. Specify the name of your output file by using the edit control.
Specify the first file to be linked	-f	Select Settings from the msdev Build menu. Select the Link tab in the Project Settings dialog box. Specify the first file to be linked by using the edit control.
Specify the last file to be linked	-1	Select Project from the msdev menu. Select the Link tab in the Project Settings dialog box. Specify the last file to be linked by using the edit control.
Specify a resource manager	-r	Access the BuildTuxedo GUI. Access the BuildTuxedo Test window and select the Resources tab. In the Tuxedo Resource Manager field, enter the name of the resource manager.
Specify services that will be available on a server	-s	Access the BuildTuxedo GUI. Access the BuildTuxedo Test window and select the Services tab. In the Service Names field, enter the name of each service on a separate line.
Use the COBOL compiler	-c	COBOL is unavailable.

To modify the build environment in an integrated development environment, follow these steps:

1. Choose Settings from the msdev Project menu.
2. Select the C/C++ or Link tab.

Note:

CC and CFLAGS are no longer needed.

To specify the library and include paths in an integrated development environment, follow these steps:

1. From the MSDEV Tools menu, choose Options to display the Options dialog box.
2. In the Options dialog box, select the Directories tab.