package bap-dependencies

Not available on OCaml 5.5
  1. Overview
  2. Docs
Analyzes program dependencies

Install

dune-project
 Dependency

Authors

Maintainers

Sources

v2.5.0.tar.gz
sha256=9c126781385d2fa9b8edab22e62b25c70bf2f99f6ec78abb7e5e36d63cfa4174
md5=5abd9b3628b43f797326034f31ca574f

Description

The command outputs program dependencies such as libraries and symbols. The information is collected recursively with various output options, including dependency graph, YAML, JSON, and SEXP.

The information includes the list of imported libraries as well as sets of imported and exported symbols. The information could be collected recursively when the --recursive option is specified. In a recursive mode, the list of paths where to search for libraries could be specified with the --library-path option that accepts a list of paths. It is also possible to use the host ldconfig cache (or specify custom library config) via the ldconfig parameter. Information about each individual dependency is cached, so consecutive calls to bap will reuse the available information and terminate quickly.

Added to opam-repository:

Dependencies (7)

  1. bap-main = "2.5.0"
  2. ogre = "2.5.0"
  3. regular = "2.5.0"
  4. bap-std = "2.5.0"
  5. ppx_bap
  6. core_kernel >= "v0.14" & < "v0.16"
  7. ocaml >= "4.08.0"

Dev Dependencies

None

Optional Dependencies

None

Used by (1)

  1. bap-core >= "2.5.0"

Conflicts

None

Build status

Results of building bap-dependencies with each compiler on check.ci.ocaml.org, run of against opam-repository 8a77e58. All results for this package.

Each result links to its build log. To keep crawlers from overloading the site, build logs require a GitHub sign-in (see ocurrent/opam-health-check). On your first log, GitHub asks you to “Authorize opam-health-check”, the OCurrent app that runs these checks; it sees only your public profile, not your repositories. The sign-in lasts 30 days.

Version OCaml 4.11 OCaml 4.14 OCaml 5.2 OCaml 5.4 OCaml 5.5
2.5.0 (this version) good good n/a n/a n/a
  • good Package successfully built
  • partial One of the dependencies failed to build
  • bad Package failed to build
  • n/a Package is not available in this environment
  • internal Internal failure