User-Defined Version Information - Analog Devices VisualDSP++ 3.5 Manual

An archive without version information will not have the
entry. The only operations on the archive using
sion information are those that use the
without version information will not pick up version information unless
you specifically request it.
If an archive contains version information (
operations on the archive preserve that version information, except opera-
tions that explicitly request version information to be stripped from the
archive (see "Removing Version Information from an Archive" on
page 6-9).
If an archive contains version information, that information can be
printed with the
elfar –p lib.dlb
::User Archive Version Info: Steve's sandbox Rev 1
a.doj
b.doj
To highlight the version information, precede it with "::".

User-Defined Version Information

You can provide any number of user-defined version values by supplying a
text with those values. The text file can have any number of entries. Each
line in the file begins with a name (a single token, for example,
not-embedded white space), followed by a space and then the value associ-
ated with that name. As an example, consider the file
my_name neo
my_location zion
CVS_TAG matrix_v_8_0
other version value can be many words; name is only one
This file defines four version names:
. The value of
other
can be many words; name is only one
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
command.
-p
is
my_name neo
elfar
switch. That is, an archive
–t
__version.doj
,
my_name my_location
; the value of
other
".
Archiver
__version.doj
that will add ver-
is present), all
:
foo.txt
, , and
CVS_TAG
is "
version value
6-7