DSEE Full Build Names:
full_build_name
Identifies the BCTs and derived objects produced as a result of an earlier build
command.
Formats
build_unit_specifier!build_version
build_unit_specifier!
build_unit_specifier!release_directory_pathname
!release_directory_pathname
Description
Full_build_name is the name of an earlier build. Full build names take four
forms:
o build_unit_specifier!build_version, for example
mysys!10-Apr-1985.10:22:37, to indicate a recent build in a binary
pool
o build_unit_specifier!, for example utils!, to indicate your last build
of the build unit
o build_unit_specifier!release_directory_pathname, for example
mysys!/rels/r1, to indicate a build in a release area
o !release_directory_pathname, for example !//art/rel_area, to indicate
the top-level built component in a release area
When you use the third syntax to reference a released build in a full build
name, the left-hand side of the full build name must identify the built
component by its name in the release area. If you renamed a component when
copying it to the release area (either because of context conflict or because
another released component had the same leaf name), refer to the component in a
full build name by the name you assigned it. (Type help create release for a
full discussion of supplying aliases for released components.)
The build_unit_specifier!release_directory_pathname syntax can be used only for
built components referenced in the -export clause of either a create release or
edit release command. If you did not include the build unit specifier of the
top-level component of the build that you are releasing in an -export clause,
you must use the fourth syntax above to reference it. For example, if you
created your release area with
DSEE> create release //art/rel_area main!21-Mar-1985.12:02:33 -export proto
you refer to the released build of proto as proto!//art/rel_area, and you refer
to the released build of main as !//art/rel_area.
The create release, compare builds, examine build, export, and create
environment commands take full build names as arguments.
Type help build_unit_specifier, help build_version, or help
release_directory_pathname for more information on the components of a full
build name.