Vector35 / Vector35/binaryninja-api
Add concept of Exporters
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
We should add a system for exporting information from/about a BinaryView via the API and UI
We should be able to export to:
- Type library (https://github.com/Vector35/binaryninja-api/issues/2772)
- DWARF (https://github.com/Vector35/binaryninja-api/issues/3863)
- Types as header
- Hex dump
- Original binary
Also, add the ability for users to implement their own exporters
The interface should look something like
exporter = get_exporter_by_name('hexdump')
print('Default columns:', exporter.get_option('columns'))
exporter.set_option('columns', 32)
exporter.set_option('upper_case', True)
exporter.export('/tmp/outfile.bntl', bv)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed get_exporter_by_name entry point and the linked issues for type-library and DWARF export. The issue does not name files or tests, and the scope spans an exporter interface, several export formats, UI integration, and user-defined exporters. Done would require an agreed design and implementation for the listed export targets and extension mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- api, reverse-engineering, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100