#cc #packages #source #analysis #implicit #system #identifying

app dapper

Dependency Analysis Project - identifying dependencies in C/C++ code and packages on filesystems

1 unstable release

0.0.0-pre.0 Nov 22, 2024

#237 in Development tools

Download history 7/week @ 2024-09-21 3/week @ 2024-09-28 2/week @ 2024-11-02 56/week @ 2024-11-16 69/week @ 2024-11-23 3/week @ 2024-11-30 3/week @ 2024-12-07

131 downloads per month

MIT license

13KB
76 lines

DAPper

DAPper helps identify the software packages installed on a system, and expose implicit dependencies in source code.

The main tool for end users parses source code to determine packages that a C/C++ codebase depends. In addition, datasets mapping file names to packages that install them for various ecosystems are provided. The tools used to create those datasets are also available in this repository.

Getting Started

Installation

For now, the main way to install DAPper is compiling from source.

  1. Clone DAPper
git clone git@github.com:LLNL/dapper.git
  1. Compile DAPper:
cargo build
  1. Run DAPper:
cargo run <source code directory or file>

Usage

Run ./dapper <source code directory or file>. The output will be the #included files from each C/C++ source code file found.

Support

Full user guides for DAPper are available online and in the docs directory.

For questions or support, please create a new discussion on GitHub Discussions, or open an issue for bug reports and feature requests.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

For more information on contributing see the CONTRIBUTING file.

License

DAPper is released under the MIT license. See the LICENSE and NOTICE files for details. All new contributions must be made under this license.

SPDX-License-Identifier: MIT

LLNL-CODE-871441

Dependencies

~35MB
~865K SLoC