Automatic project creation for archive formats

[emesare]

What is the feature you'd like to have?
When dealing with static libraries (.lib, .a, .rlib) the current workflow is to manually unarchive and load individual object/binary files, possibly into a project. This is especially cumbersome for producers of WARP signatures as they either have to use a headless script or run signature generation for each of the possibly thousands of object files.

A possible solution to this would be to have a handler where when an archive of files is opened with Binary Ninja we create a project including all the files of the archive. This would have to be a separate behavior to the open file handlers as they return a single BinaryView.

Is your feature request related to a problem?
Currently WARP uses an external "script" (see: sigem.rs) to generate signatures for static libraries. This is not user friendly as you need to go and build it and use separately from the Binary Ninja UI. A better workflow would be:

1. Open mylib.lib in Binary Ninja
2. Automatically create project with the object files
3. Run "WARP\Create signatures for project"