wguiwide.gml

开放源码的编译器open watcom 1.6.0版的源代码

.chap &wide
.*
.if &e'&dohelp eq 0 .do begin
.section Introduction
.*
.do end
.*
.np
.ix '&ide'
Software development normally involves managing a number of different
files for each project. A project often includes multiple source
files, include files, and libraries. In addition, there are usually
several programming tools involved: compilers, linkers, preprocessors,
debuggers, editors, and so on. But this is likely not new to you. What
will be new is the &wide (&vip).
.np
The &wide is a software development tool that manages project files
and language tools. Although it is really a tool itself, the common
term to describe it (and possibly the best analogy) is
.us Development Environment.
By using the &wide, you have direct access to each of the files
relating to a project and all of the language tools you require to
build your application.
.np
:HBMP 'ide_s.bmp' c
.*
.section How the Environment Operates
.*
.np
.ix '&ide' 'environment'
The &wide has a graphical interface that combines file management and
tool management. An &vip session deals with a
.us Project.
A project can be generally defined as the collection of files and
necessary information that relates to the development of project
components. However, a project is more than just a graphical
representation of a file list&mdash.it contains all of the underlying
smarts to understand the interrelation of all files associated with
the project and to ensure that these files are up-to-date.
.np
Each project component is referred to as a
.us Target.
An &ide target is made up of the source files, include files,
libraries, and MAKE instructions to create the target file (for
example, ".exe", ".dll", ".lib", or ".hlp"). A project often has more
than one target. Each target can be set to create the associated
target file for a specific destination platform.
.np
Within a target, there are
.us Sources.
A source is an individual file (such as a ".c" or ".cpp" file, but it
can also be a ".bmp", ".rc", or ".lib" file) used to create the target
file. A target usually has more than one source.
.*
.section How the &ide Looks
.*
.np
.ix 'look and feel of the &ide'
In the following illustration, the main window is the project window
for a project entitled
.fi first.wpj.
The sub-window represents the target for this project,
.fi target.exe.
The source file for the target is listed within the target window. In
this project, there is only a single target with a single source file.
.figure *depth='3.8' *scale=60 *file='ide1' The &company &vip window displays project and target windows.
.np
The language tools are available on the toolbar and the drop-down
menus. For example, on the Sources menu, you can work with the source
that is selected in the target window. Here you can add a new source,
remove or rename an existing source, edit a source, and so on. A
similar set of target actions are available in the Targets menu and
project actions are located in the File menu.
.np
A single &vip session displays a project. If the project consists of a
number of components, such as two executables and one library, these
appear as target sub-windows on the project window. Each target window
displays the files necessary to construct the target and associates
files with a rule describing the construction mechanism based on
filename extension. For example, a filename with the extension ".exe"
may associate with the rule for constructing executables, or a
filename with the extension ".lib" may associate with the rule for
constructing static libraries.
.np
Different projects can refer to the same target. If they do, either
project can manipulate the shared target and any changes to either
project affect the shared target.
.*
.section The Files the &ide Uses
.*
.np
.ix 'projects'
The &wide creates and manages a project, referencing a number of
targets. The &vip uses filename extensions to represent projects and
targets. The extension ".wpj" represents projects and the extension
".tgt" represents targets. The &vip compiles and links the target in
the target directory.
.np
The project file (.wpj) contains the names of all of the target files
related to the project, including housekeeping information about the
project and the current &vip session.
.np
Each target file (.tgt) describes one target and includes the name and
type of the target executable, a reference to a rule describing how to
build the target, and a list of relevant switches the rule uses. In
addition, target files also contain the names of all of the source
files used to construct the target program, references to similar
rules for compiling them, and relevant switches.
.np
In constructing targets, the &ide references a list of rules defined
in a configuration file, called
.fi &vip_cfg..
Each rule defines a command line used to do the construction and a
list of actions you can perform on the target program (such as make,
run, or debug) or on the files in the item list (such as make or
edit). Additionally, rules refer to tools.
.np
Tools define which command line switches you can use in the &wide..
.*
.section Using the &wide
.*
.np
.ix '&ide' 'using the'
This section discusses the following topics:
.begbull $compact
.bull
Starting the &wide
.bull
Quitting the &wide
.bull
The &vip Menu Bar
.bull
The &vip Status Bar
.bull
The &vip Toolbar
.endbull
.*
.beglevel
.*
.section Starting the &wide
.*
.np
.ix '&ide' 'starting the'
To start the &ide, double-click on the &vip icon. This opens the
&company &vip Project window.
.*
.section Quitting the &wide
.*
.np
.ix '&ide' 'quitting the'
To exit the &ide, choose Exit from the File menu of the &company &vip
Project window or double-click on the system menu box on the same
window.
.*
.section The &vip Menu Bar
.*
.np
.ix '&ide' 'menu bar'
.ix 'menu bar' '&ide'
The &vip's menu bar consists of the following eight menus:
.begpoint
.point File
Open new or existing projects, close and save projects, exit the &vip,
and show or hide the toolbar and status bar
.point Actions
Make all targets, run applications, and invoke other GUI Tools
.point Targets
Work with targets, including setting switches and creating, removing,
and renaming targets
.point Sources
Work with sources, including setting switches and creating, removing,
and renaming sources
.point Options
Set switches for creating targets and sources
.point Log
Perform functions relating to the &vip Log window
.point Window
Refresh the contents of the &vip windows and view the targets currently
available on the &vip window
.point Help
Access on-line help information
.endpoint
.*
.section The &vip Status Bar
.*
.np
.ix '&ide' 'status bar'
.ix 'status bar' '&ide'
The Status Bar appears along the bottom of the &company &vip Project
window. This bar displays hint text for the toolbar button and menu
option over which your cursor is positioned. Status messages, such as
Saving, Adding, and Executing Log, appear in this bar so you are aware
of what action the &vip is performing. A check mark beside the Show
Status Bar menu option in the File menu indicates that this feature is
enabled. To disable this feature, choose the option again from the File
menu and the status bar disappears from the window.
.figure *depth='3.8' *scale=60 *file='ide2' The &vip Status Bar can be toggled from the File menu.
.*
.section The &vip Toolbar
.*
.np
.ix '&ide' 'tool bar'
.ix 'tool bar' '&ide'
In the &company &vip Project window, the toolbar appears below the
menu bar when the Show Tool Bar option in the File menu is activated
(default). A check mark beside the menu option indicates that it is
enabled. To disable this feature, choose the option again from the
File menu and the toolbar disappears.
.figure *depth='0.42' *scale=100 *file='ide3' You can access thirteen &vip functions from the toolbar.
.np
The following explains the function each icon performs, as well as the
equivalent function on the menu bar.
.begpoint $break
.point Create
:HBMP 'newproj.bmp' i
.ix 'new project'
Create a new project. This is equivalent to the option New Project in
the File menu.
.point Open
:HBMP 'openproj.bmp' i
.ix 'open project'
Open an existing project. This is equivalent to the option Open
Project in the File menu.
.point Save
:HBMP 'saveproj.bmp' i
.ix 'save project'
Save the current project. This is equivalent to the option Save
Project in the File menu.
.point Edit
:HBMP 'edititem.bmp' i
.ix 'edit text'
Edit the selected source file. This is equivalent to the option Edit
Text in the Sources menu.
.point Make Source
:HBMP 'makeitem.bmp' i
.ix 'make source'
Make the selected source file. This is equivalent to the option Make
in the Sources menu.
.point Make Target
:HBMP 'maketarg.bmp' i
.ix 'make target'
Make the current target. This is equivalent to the option Make in the
Targets menu.
.point Run
:HBMP 'runtarg.bmp' i
.ix 'run target'
Run the current target. This is equivalent to the option Run in the
Targets menu.
.point Debug
:HBMP 'debgtarg.bmp' i
.ix 'debug target'
Debug the current target. This is equivalent to the option Debug in
the Targets menu.
.point Remote Debug
:HBMP 'rdbgtarg.bmp' i
.ix 'remote debug target'
Debug the current target on a remote machine. This is equivalent to 
the option Remote Debug in the Targets menu.
.point Browse
:HBMP 'browtarg.bmp' i
.ix 'browse target'
Browse the current target. This is equivalent to the option Browse in
the Targets menu.
Currently, browsing is supported by the &watc compilers only
(&watf does not support browsing).
.point Sample
:HBMP 'samptarg.bmp' i
.ix 'sample target'
Run and sample the current target. This is equivalent to the option
Sample in the Targets menu.
.point Profile
:HBMP 'proftarg.bmp' i
.ix 'profile target'
Profile the current target. This is equivalent to the option Profile
in the Targets menu.
.point Make All
:HBMP 'makeproj.bmp' i
.ix 'make all targets'
Make all targets in the project. This is equivalent to the option Make
All in the Actions menu.
.endpoint
.*
.endlevel
.*
.section Getting Started with a Short Tutorial
.*
.np
.ix '&ide' 'tutorial'
.ix 'tutorial' '&ide'
Perhaps the easiest way to understand how the &wide manages an entire
project's files and tools, is to work through a brief example.
In this walk-through, you create and execute a simple C program using
the &vip..
FORTRAN developers can follow along substituting FORTRAN code and file
names where appropriate.
The session will help you understand the basic concepts of the &vip
and the steps involved in project development.
.np
The illustrations shown in this section are taken from the Windows
environment. The OS/2 environment is very similar with some minor
differences. For example, in the OS/2 environment the IDE uses the
OS/2 Editor rather than &company's Windows Editor. Although this
tutorial builds a Win32 executable, you can choose to build a Win16 or
OS/2 PM executable. The procedures to follow are not that much
different. When the time comes to select the type of target, simply
choose an environment that you can run on your machine so that you can
run your application to make sure it works.
.*
.beglevel
.*
.section A Simple Executable
.*
.ix '&ide' 'defining a project'
.begstep
.step Double-click on the &vip icon
in the &company Tools window.
.result
The &company &vip Project window appears.
.ix 'new project'
.step Choose New Project
from the File menu.
.result
The Enter Project Filename dialog appears. The default project name is
.fi noname.wpj.
.step Enter the filename
.fi \project\first
in the File Name field and click on OK.
.figure *depth='3.11' *scale=84 *file='ide4' Enter the filename in the Enter Project Filename dialog.
.result
This is the name of the project you are creating. If you enter a
directory that doesn't exist (in this case,
.fi \project
.ct ),
the &vip reveals a message box asking if you want to create the
specified directory.
Click on OK to create the specified directory and project file.
.begnote
.note Note:
The &vip looks for existing projects with the new name. If a project
with the specified name already exists, the &vip will prompt you
rather than simply overwriting the existing project.
.endnote
.np
The project name appears in the title bar of the &company &vip Project
window. Note that the &vip added the extension ".wpj" to the project
name. The New Target dialog appears on the screen where you define a
target for the new project.
.step Enter the desired target name
in the Target Name field (we suggest
.mono target1
.ct ).
Next, select the appropriate Target Environment (we suggest
"Win32") and Image Type (we suggest "Character-mode Executable").
Click on OK when completed.
.figure *depth='3.24' *scale=64 *file='ide5' Select target name, target environment and image type
.result
The New Target dialog closes and the &vip creates a target window
entitled
.mono target1.exe
for the new target. Note that the &vip appends the appropriate
extension to the target name for you once you click on OK. You can now
add sources to the target.
.step Choose New Source
from the Sources menu.