Vector35 / Vector35/binaryninja-api

Persisted type parser settings and simple include directories

Open
#7,132 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: Database Component: Type Parser Component: UI Effort: Low Impact: Medium
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

Currently you define include directories in the clang arguments, this is OK but it becomes a little annoying to work with if you are constantly defining new types, it would be nice to persist these somewhere, possibly in the view.

Image

Other tools like IDA have "compiler options" which define these include directories as a seperate config option, which lets them use a file picker, which is preferred!

They also store these compiler options in the database along with predefined macros.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the existing clang argument and type-parser settings, then trace how views and databases persist configuration; done should include persistent include directories and predefined macros with a file-picker workflow, but the exact scope needs clarification.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
reverse-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.