Introduction
Generating tags file according to the DWARF debug information in the binary file.
Prerequisites
SQLAlchemy
SQLite3
Installation
# Ubuntu
apt install sqlite3
# ArchLinux
pacman -S sqlite3
pip install btagsUsage
btags.py -j 2 -c /dir/to/the/build/root /path/to/the/binary-j max worker threads
-c specify the directory under which the binary is compiled
After, you will get a tags file under current working directory.
It can be used as following
vim -t mainFor examples Assume there is a autoconf project under dir /tmp/project, and you use the following command to build it.
cd /tmp/project
mkdir build
cd build
../configure
makeThen, /tmp/project/build will be the build root, because the project is compiled under this directory.
TODO
[] Replace sqlite with other faster data store mean
[] Add test cases
[] Add Travis CI support
1 maintainer
Metadata
1 maintainer
Release files for btags 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| btags-0.1.1.tar.gz | 14.3 kB | Without provenance | Details for btags-0.1.1.tar.gz |
Security for btags 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
