Problem: The tool can currently create new configuration profiles, but separate Binary Ninja installations must happen manually outside of the tool (though bn-loader can share installations across profiles).
Proposed Solution: When a user invokes bn-loader init, they should optionally be able to provide the path to a downloaded release of Binary Ninja (e.g. the EXE installer on Windows or the ZIP for Linux builds). It should then unpack this to the requested "installation directory".
Problem: The tool can currently create new configuration profiles, but separate Binary Ninja installations must happen manually outside of the tool (though bn-loader can share installations across profiles).
Proposed Solution: When a user invokes
bn-loader init, they should optionally be able to provide the path to a downloaded release of Binary Ninja (e.g. the EXE installer on Windows or the ZIP for Linux builds). It should then unpack this to the requested "installation directory".