Using the buildserver and buildclient Commands


	Corporate Info \| News \| Solutions \| Products \| Partners \| Services \| Events \| Download \| How To Buy
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Doc Home \| Platforms \| Topic List \| Previous \| Next \| Contents

Using the BEA Tuxedo System on Windows NT

Although the buildserver(1) and buildclient(1) commands are available on the Windows NT platform, there are differences between how the options to these commands work on NT platforms and non-NT platforms. The following table lists these differences.

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

-l

Select Settings from the msdev Build 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 page.
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 page.
In the Service Names field, enter the name of each service on a separate line.

Use the COBOL compiler

-c

COBOL is unavailable.

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	-l	Select Settings from the msdev Build 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 page. 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 page. 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: (a) select Settings from the msdev Build menu, and then (b) select either 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, select Options from the MSDEV Tools menu. From the Options dialog box, select the Directories tab.