-
Per some discussion in the Binary Ninja Slack, it seems the only way to have types/variables/system calls associated with a Platform is using platform type definitions, which currently reside in either I've tried adding the types to a type library as an alternative, but even when explicitly associating those types with a platform, they don't get picked up as part of the platform's system calls, types and variables. This is particularly a problem for system calls, which seemingly aren't possible to define in other ways currently. It sounds like there were plans to add APIs to handle this, but this issue relating to that hasn't been updated in a while: #1936 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
This actually looks like I just forgot to close out issues when I added support. When defining the Platform it's now possible to provide a path to a header file to use that you keep inside your plugin directory: binaryninja-api/python/platform.py Line 60 in 6812c97 |
Beta Was this translation helpful? Give feedback.
This actually looks like I just forgot to close out issues when I added support. When defining the Platform it's now possible to provide a path to a header file to use that you keep inside your plugin directory:
binaryninja-api/python/platform.py
Line 60 in 6812c97