Return to Claw Introductory Edition Download page
Claw Builder Introductory version - Instructions
(The following is the contents of the CbldRead.Txt file included
with the Claw Builder Introductory version).
Installing the Claw Builder:
Cbld_Intro.Zip (Introductory builder & documentation file)
Cbld_Sample13.Zip (Sample project and source)
We assume that the Claw Introductory Edition has already been installed properly.
(Note: If you do not want to compile and run code generated by the builder, installing
the Claw Introductory Edition is not necessary.)
- Create a directory to hold the builder. We will use \Claw\Cbuild in our
examples, but you may use anything you wish. Create a subdirectory of
the program called "Sample".
- Unzip Cbld_Intro.Zip into
- Unzip Cbld_Sample13.Zip
into \Claw\Cbuild\Sample. If the two sample source
files do not have a long file name, rename them appropriately:
ren Sample~1.ads Sample_Custom-Valid.Ads
ren Sample~1.adb Sample_Custom-Valid.Adb
- The builder is self-registering. However, you can better match the default
settings to your compiler by manually registering it. Do this by running
"CBuild /INSTGB" from the command line (for GNAT), "Cbuild /INSTOB" for
ObjectAda, "CBuild /INSTAB" for Rational APEX, or "CBuild /INSTJB"
for Janus/Ada. Note that the option must be given in all capital letters.
If you don't want desktop and start menu icons for the Claw Builder,
remove the 'B' from the /INST option.
- We're now going to generate the sample application, in order to verify that
the Claw Builder was installed properly.
Open CBuild. Select "Open", then navigate to \Claw\Cbuild\Sample. Select
the Sample project file. Select "Project","Properties" from the main menu.
Go to the "Files" page, and change the "Generated code output path" to
D:\Claw\CBuild\Sample, where D: is the disk name for the drive where you
installed CBuild. You can use the Browse button to make this easier.
While we're in the project, we also should correct the help file path.
Switch to the "Help" page, and change the "Application Help Path", again
to D:\Claw\CBuild\Sample. Press "OK" when you're done.
- Select "Project" "Generate Code" from the main menu. The sample code should
now be generated. Select "File" "Save" to change the sample project file.
(We save the file to save the path changes you made above).
- The next step depends on the compiler you have. Follow the appropriate
directions for your compiler.
- For Janus/Ada, modify the Init.Bat file to point at the location of
the Claw object files. This appears as \Claw\Object in the file.
Make sure that the paths and environment variables for Janus/Ada are
Run Init.Bat to set up the project, then run Comp.Bat to compile the
- For GNAT, go to a DOS window. Change directories to \Claw\Sample.
Make sure that your Ada_Include_Path, Ada_Objects_Path, and Include
environment variables are properly set for Claw programs. (This
means that "\Claw\Source" should by included in each of those variables).
Compile the sample application with the command:
gnatmake -O2 -gnato sample.ada -largs -mwindows my_app.rbj
Note: You may need to process the generated .Rc file in order for this
command to succeed. The tool GNAT provides to do this (RCL) does not
work reliably, so you will have to get the tools from some other source.
(The free version of ObjectAda for Windows has the appropriate tools.)
Because we don't know what tools you will use, so we can't provide
directions for processing the .Rc file. We have processed the .RC file
for the sample application and produced my_app.rbj. You'll have to do
it for your own applications.
- For ObjectAda, create a project.
Use 'project' 'settings' 'link' to select Window (rather than Console).
Use 'project' 'settings' 'search' and include <objectada>/win32ada/binding
and <objectada>/apilib (where <objectada> denotes the CDROM drive
or disk path where these are to be found).
Use 'project' 'settings' 'search' to include the Claw project.
Use 'project' 'settings' 'files' to include all Sample source files.
Also include My_App.res. (If you don't have My_App.res, create it by
running rc on My_App.rc -- "rc My_app.rc").
"Build" Sample.Ada, which will compile the Sample program.
- For Rational APEX, create a view in the Claw_Examples subsystem.
Return to the Claw Builder. Check that the global option for APEX
pragmas is set (find it in "Project" "Options" on the "Miscellaneous"
page). Reset the "Generated code output path" (in the project properties)
to point at the subdirectory of the new view. Select "Project"
"Generate Code" from the main menu to generate the code directly into
this view. If needed, open the APEX GUI. Navigate to the sample view.
Select "Compile" "Resource", and run the resource compiler on My_App.rc.
Select "Compile" "Link" to link the main program "Sample"; this will
compile all of the needed sample files.
- Now (for all compilers), run the application from the command line by
typing "Sample". Note that the programmer provided routines which make
up "Sample" mainly Beep (in different tones on Windows NT, but all of the
same on Windows 95) when they are called.
- If you've gotten this far, you're ready to start using the builder.
You probably will want to read the overview and tutorial for the builder
in the builder help. (Use "Help"/"Help Topics" in the builder to get to it.)
Next, familiarize yourself with the builder by playing with the sample
application. Finally, you can build your own applications.
To deinstall Claw Builder, simply run "CBuild /UNINST" from a command line
prompt. (This will remove the registry entries used by the builder.) Then,
delete the files. Note that "UNINST" must be in capitals; otherwise, you
will see a "file not found" error. Then the Builder files can be deleted.
Note that the full version of Claw has a standard Uninstall program.
Projects created with the Introductory builder can be loaded into the full
version of the builder. The builder automatically will make any conversions
necessary. Similarly, programs written to use the Introductory version of Claw
can be used with the full version of Claw.
Updated December 20, 2000 by webmaster.
Copyright © 2000 RR Software, Inc.