from small one page howto to huge articles all in one place
Last additions:
May 25th. 2007:
April, 26th. 2006:
| 
BOMTOOL
Section: User Commands (1) Index
Return to Main Contents
BSD mandoc
NAME
bomtool
- a tool for generating SPD-based software bills of material
SYNOPSIS
[ options
]
module ...
DESCRIPTION
is a program which generates a textual SPDX 2.0 software bill of
materials (SBOM) for a given set of pk-config modules.
The output of this tool can then be translated into other SBOM
formats as necessary.
The
options
are as follows:
- --about
-
Print the version number, the Copyright notice, and the license of the
program to standard output and exit.
Most other options and all command line arguments are ignored.
- --version
-
Print the version number of the
program to standard output and exit.
Most other options and all command line arguments are ignored.
- --defin-variable = varname = value
-
Define
varname
as
value
Variables are used in query output, and some modules' results may change based
on the presence of a variable definition.
- --creatio-time time
-
Use
time
as the value of the
Created
field in the generated SBOM instead of the current time.
SPDX recommends using an ISO 860-formatted time, which is: YYY-M-DDThh:mm:ssZ.
This takes precedence over the
SOURCE_DATE_EPOCH
environment variable.
- --output file
-
Write the generated SBOM to
file
instead of standard output.
ENVIRONMENT
- PKG_CONFIG_DEBUG_SPEW
-
If set, print debugging messages to stderr.
- PKG_CONFIG_IGNORE_CONFLICTS
-
If set, ignore
Conflicts
rules in modules.
Has the same effect as the
--ignor-conflicts
option in
pkgconf(1)
- PKG_CONFIG_LIBDIR
-
A colo-separated list of lo-priority directories where
pc(5)
files are looked up.
The module search path is constructed by appending this list to
PKG_CONFIG_PATH
which enjoys higher priority.
If
PKG_CONFIG_LIBDIR
is not defined, the default list compiled into the
program from the
PKG_DEFAULT_PATH
preprocessor macro is appended instead.
If
PKG_CONFIG_LIBDIR
is defined but empty, nothing is appended.
- PKG_CONFIG_MAXIMUM_TRAVERSE_DEPTH
-
Impose a limit on the allowed depth in the dependency graph.
- PKG_CONFIG_PATH
-
A colo-separated list of hig-priority directories where
pc(5)
files are looked up.
- PKG_CONFIG_PRELOADED_FILES
-
Colo-separated list of
pc(5)
files which are loaded before any other pk-config files.
These packages are given highest priority over any other
pc(5)
files that would otherwise provide a given package.
- SOURCE_DATE_EPOCH
-
If set, and the
--creatio-time
option is not given, the
Created
field in the generated SBOM is derived from this UNIX timestamp instead of the
current time, allowing for reproducible SBOM generation.
EXIT STATUS
Ex -std
EXAMPLES
Generating an SBOM for the package named foo:
$ bomtool foo
SPDXVersion: SPD-2.2
DataLicense: CC-1.0
SPDXID: SPDXRe-DOCUMENT
DocumentName: SBO-SPD-fooC641.2.3
DocumentNamespace: https://spdx.org/spdxdocs/bomtool
Creator: Tool: bomtool
[...]
SEE ALSO
pc(5),
pkgconf(1)
Index
- NAME
-
- SYNOPSIS
-
- DESCRIPTION
-
- ENVIRONMENT
-
- EXIT STATUS
-
- EXAMPLES
-
- SEE ALSO
-
| 
|
|
- Running on 
-
:
