Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simple import handling for when flowslicer is installed as a package #1

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jprokos26
Copy link

Allows python -c “import flowslicer” to be run from either the local directory without any package installation (existing functionality) as well as supporting flowslicer to be installed as a package to be run anywhere (new functionality).

This PR does not include the setup.py file necessary for generating the package as I installed this as a submodule within a separate package using setuptools.find_packages(). See this example to see how I included flowslicer within my own setup.py.
Note, a better/clearer change would be to set up flowslicer to be a python package such that the try block is unnecessary but I did not want this PR to change any existing functionality, only to add new.

@jprokos26
Copy link
Author

jprokos26 commented Jan 30, 2023

To clarify why I needed this change, I could not find an easy way to call flowslicer within BinaryNinja to view the output of calling DataFlowILFunction.graph(). Getting it running within binaryninja was my solution for which I have not determined if the graph part works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant