Builder Xcessory tailors itself to your development environment, and is just one of the many tools that you use during the design, implementation, and maintenance of your application. This section describes how to integrate Builder Xcessory with other tools.
Integrating Builder Xcessory with Your Environment
Builder Xcessory is one of many tools that can be used in the design and implementation of an application. Rather than attempting to provide the entire environment for application development, Builder Xcessory integrates with the tools in your own environment.
If you use SunSoft Workshop, Silicon Graphics Developer Magic or DEC FUSE you can install Builder Xcessory into your environment. You can then access the tools in your environment from within Builder Xcessory. Integrating with these tools greatly expands the capabilities and usefulness of Builder Xcessory when used throughout a project cycle.
Once installed in your development environment, you can start Builder Xcessory, use Builder Xcessory to work on user interface design, and access other development tools in your environment directly from Builder Xcessory. For example, you might start up Builder Xcessory from your environment and design a small portion of a user interface, test it in Play Mode, use your environment's debugger to debug it, and then return to Builder Xcessory to continue working on your user interface design.
Before you can use Builder Xcessory with the tools in your development environment, you must first install Builder Xcessory into your environment. Refer to the Builder Xcessory Installation Notes for a detailed description of the installation process.
Note: If you wish to use Builder Xcessory with DEC FUSE tools, you must start Builder Xcessory from the DEC FUSE control panel. There is no command-line switch to allow Builder Xcessory to initialize DEC FUSE communication.
Note: When working with Workshop, you need to launch Builder Xcessory from Workshop in order to control the Builder Xcessory windows from the Workshop Manager.
The SGI Developer Magic tools can be invoked separately or from a small tool control panel. The tools use ToolTalk as a system for passing messages. For example, the debugger can tell the editor to load a file.
Note: Unless otherwise noted, all customization options are saved between invocations of Builder Xcessory.
When developing an application in Builder Xcessory, you can use your environment's build or make tool at any time. You must tell Builder Xcessory which tool you want to use, verify that your makefile parameters are correct, and then execute a build of your application.
3. If you want to use CodeCenter or ObjectCenter to manage the build instead of the environment-provided tool, select Use CenterLine Tools from the Debugger and Build Manager tab (see Debugger & Build Manager with Centerline Defaults ).
Note: If you are using a CenterLine tool to manage the build, the language you chose specifies the command line used to start the tool. (Generating C or UIL/C uses the C command. Generating C++ or ViewKit uses the C++ command.)
4. Verify the make parameters by selecting Code Generation Preferences from the Browser Options menu to display the Code Generation Preferences dialog, and then clicking the Makefile tab ( Makefile Tab on the Language Settings Dialog ).
Note: If you are using Builder Xcessory outside of a development environment and Code/ObjectCenter is not available on your platform, Make Application is not available. Instead, you must run the make command manually.
This example assumes you are using Builder Xcessory with DEC FUSE, Developer Magic, or Workshop, and you are ready to execute a build of your application in C. (The procedure is similar in other languages.)
Note: If the DEC FUSE Builder is not already running, it starts automatically. The first time it runs, you must enter the Makefile name in the configuration dialog. In any subsequent session it is not necessary to enter the Makefile name.
2. Click on the Debugger & Manager tab ( Debugger & Build Manager Tab on the Tools Customization Dialog ):
5. Click on the Makefile tab ( Makefile Tab on the Language Settings Dialog ):
Note: On platforms that support Code/ObjectCenter, you can use Code/ObjectCenter instead of the environment's make manager.
Note: Select Use CenterLine Tools if you prefer to use CodeCenter or ObjectCenter rather than your environment's debugger.
- Setting the toggle causes Builder Xcessory to try to start a CenterLine tool if Builder Xcessory cannot communicate with a currently running process.
- Unsetting the toggle causes Builder Xcessory to cease attempting to communicate with a currently running process.
While using Builder Xcessory, you can check out and check in files from a source code control system without exiting Builder Xcessory. If you are using Builder Xcessory from a development environment, you can access that environment's source code control system. If using Builder Xcessory as a stand-alone program, you can use RCS, CMS, SCCS, ClearCase, or a system you specify. If properly configured, Builder Xcessory can automatically check out UIL files under Source Control.
1. Select Tools Preferences from the Browser Options menu to display the Tools Customization dialog ( Tools Customization Dialog).
3. If you want Builder Xcessory to automatically ask you whether or not to try to check out read-only UIL files when they are read in, set the Check Out Read- Only Files toggle. Otherwise, Builder Xcessory will read the file but not overwrite it.
Note: The commands text fields are only sensitive if the Source Code Control option is set to a source control system . For more information, see Editing the Commands for Source Code Control .
Builder Xcessory processes the command before executing it, in order to substitute any options you set on the Check In and Check Out dialogs (Browser:Project). (These dialogs are discussed in detail in Using a Source Code Control System .)
- %file[option_specification %s]
- %version[option_specification %s]
- %comments[option_specification %s]
For example, you can specify a version string for a file in both the Check In or Check Out dialogs. How this string is passed to the source code control commands varies from system to system. Suppose the check out command for the source code control system you are using is
check_out , and in order to specify a version to check out you would enter:
When Builder Xcessory attempts to check out a file, it looks for
%version in the command string. If you have specified a version string in the dialog, Builder Xcessory will add the option you specified within the square brackets and replace the
%s with the string entered in the Check Out dialog.
- You can choose one of the following options:
- · Lock a file when you check it out
- · Check out a read-only version
- · Remove a lock that you have set
- In addition, you can specify a version string number, or overwrite a read-write version of a file that is currently checked out.
1. Select Check In Source from the Browser Project menu. This displays the Check In dialog, as shown in Check In Dialog .
Note: The only error-checking tools currently available for Builder Xcessory are Purify and MemAdvisor.
2. Click on the Test Tools tab ( Test Tools Panel on the Tools Customization Dialog ):
When you select a test tool, Builder Xcessory adds targets for that tool to the makefile. When you build your code, you can use the pure target to build an instrumented version of your application. When you run your application, the error-checking tool provides information about memory usage and errors in the object code. The executable provides information about memory leaks and accesses.
Builder Xcessory uses the tool
emacsclient to tell Emacs to load a file and display the buffer. Emacs must be running. Builder Xcessory issues a request of this "Edit Server". By default, Emacs is not configured to run as a server. In order for the
emacsclienttool to work, you must add the following Emacs Lisp command to your
.emacs file (the file that
emacs runs at startup):
emacs to run on one system and the client program to make edit requests from another system, you can use
gnuclient. gnuclient works similarly to
emacsclient , but also includes the following features: