Copyright (C) 2002 Arnaud BERTRAND web-site: http://www.apvsys.org
to check the cross-references in the ApVSys database By default, only the current tool-spec will be checked to see if command versions are defined by more than 1 tool-spec line. It can cause conflict or anoying situations.
This effect is named collision. You will see this ``problem'' when a command is registered for 2 different tools. Let's take an example:
We assume that the command cpp was registered for different tool/version, the output of ``apv -a cpp'' is:
3 registered versions for the command cpp : gcc/v3.0.2 Compiler8051/v1.7 gcc/v2.95.3 <= <= <=
Matched toolspec: /home/arn/tool-spec: gcc/default Chosen version from: "gcc/v2.95.3"
The command if known for 2 different tools (gcc and Compiler8051).
If a user is using both tools... we have a collision
If his toolspec is:
the executed version of cpp will be the gcc/v2.95.3 version (see above) but if his toolspec is:
the executed version of cpp will be the Compiler8051/v1.7 version.
apv-xcheck [-h] [-v] [-t toolname] [-a]
> apv-xcheck > apv-xcheck -v -t gcc > apv-xcheck -a -t gcc
=head1 SEE ALSOapvsys-intro(1) ap-environment(1) apv(1) apv-lib(1) apv-linktool(1) apv-regtool(1) apv-setdefault(1) apv-osmirror(1) apv-nativeoscheck(1) apv-dbcheck(1)