TOC PREV NEXT INDEX DOC LIST MASTER INDEX




RCI > Create Target Libraries

This command creates a target Ada library (Target Directory) that corresponds to the specified host view. (Depending on your RCI customization, the elements of the Ada library required by your target compiler will be built, including the Ada program library and import information.)

If the Target Directory does not already exist on the target, it will be created and associated it with the selected host view. If the RCI Target Directory does exist on the target but is not an Ada library, it will be converted it into an Ada library before associating it with the host view. If the RCI Target Directory exists on the target and is already an Ada library, it will just be associated it with the selected view.

Note: (Apex/Summit) Do not assign two views from the same subsystem to the same target library, unless your customization specifically requires this structure.

Once the target library has been created, all units in the host view are marked as requiring recoding on the target.

When you create a target library for a view that is imported by others, the importing views' imports are made obsolete.

Before you compile units in one of the importing views, you must refresh its imports (use Control > Maintenance > Refresh (Apex/Summit)).

The first time you create a target library for a host view, you must specify the Target Directory.

You should also specify the Machine, if different from the host, when a target library is initially created.

Create Target Libraries Dialog Fields:

Host RCI Views: (Apex/Summit)

Use this field to specify the host view(s) for which a target library will be created.

Host RCI Subsystems: (Apex/ClearCase)

Use this field to specify the host subsystem(s) for which a target library will be created.

Check Out/In Artifacts File... Button (Apex/ClearCase)

This button opens a subdialog that allows to check out (and later check back in) the subsystem's Policy/Switches file, so that the command may update the values of the RCI specific context switches in this file.

Note: This may not be needed if the RCI specific switches are stored in a separate, non-controlled, Policy/RCI.sw switch file which is "INCLUDE'd" from the Policy/Switches file.

Machine:

Use this field to specify which machine, if different from the host on which Apex is running, performs target operations (such as library operations, compilation and linking).

This field will be used to set the value of the RCI_COMPILATION_PLATFORM context switch for the host view.

When rebuilding an existing target library, if this field is not supplied, the command uses the current value of the switch.

Target Directory specification fields:

These fields are used to specify a context, and a library name within this context, which will be combined (in a RCI customization specific way) to form the pathname for the target library to create.

This pathname will be used to set the value of the RCI_TARGET_DIRECTORY context switch for the host view.

Context for target libraries Button and Text Field

The path to the directory context for the target library.

Selecting the Context for target libraries Button will cause the Target library context is default context Button to be deselected.

Target library context is default context Button

Sets target library context to a default value.

Selecting the Target library context is default context Button will cause the Context for target libraries Button to be deselected.

The value for the default context is RCI customization dependent. Generally, if the host filesystem is visible from the target machine, this default context will be the host view's enclosing subsystem (Apex/Summit) or the host subsystem's enclosing directory (Apex/ClearCase).

Target library name Button and Text Field

The name of the target library within the context.

Selecting the Target library name Button will cause the Target library name is automatically generated Button to be deselected.

Target library name is automatically generated Button

Sets target library name within the context to a default, automatically generated, value. Selecting the Target library name is automatically generated Button to be deselected will cause the Target library name Button to be deselected.

The value for the default name is RCI customization dependent. Generally, if the host filesystem is visible from the target machine, this default name will be targets/<view:t:r>.rci<view:e> (i.e. a subdirectory within a targets directory with the same base name as the host view, and extension .rciwrk, .rcirel or .rcirss, depending on the kind of the host view).

Rebuild existing target library Button

Setting this button is exclusive from using the Target Directory specification fields, and causes them to become inactive.

It causes the RCI to first destroy the existing target library (both Ada library and directory) corresponding to the selected host view, then rebuild the specified library, with the same name (as specified by the current value of the RCI_COMPILATION_PLATFORM switch for the view).

If this option is not selected, and the new target library is in a different location from the existing target library, the existing target library is "orphaned"; that is, the host view no longer contains any information about its existence.

Note: RCI > Create Target Libraries may or may not be implemented from one RCI customization to another. Also, your customizer can modify the way it operates (in particular the rules used to analyze and combine the provided target library context and name, and to generate default values for these).

The RCI is described in the RCI User's Guide and the RCI Customization Guide.


Rational Software Corporation 
http://www.rational.com
support@rational.com
techpubs@rational.com
Copyright © 1993-2001, Rational Software Corporation. All rights reserved.
TOC PREV NEXT INDEX DOC LIST MASTER INDEX TECHNOTES APEX TIPS