-
Notifications
You must be signed in to change notification settings - Fork 54
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
Installing and running on Windows #10
Comments
Thank you for the report and helpful context @rchildre3 - we will do some digging here to see how we can improve usability. We will upstream the issue if it's Jep-specific. |
Encountered similar issue on Windows and here are the problems I noticed and my solutions for them:
The arg
This caused the DLL dependency issue on my side.
The solution in my case is:
Here is a simple wrapper to start Ghidra:
|
Thank you very much. I encountered the same problem and solved it perfectly according to the method you provided. |
To add on to this issue, I've had a similar one when attempting to load Ghidrathon using a Windows Store distribution of Python. The steps to reproduce are:
I wasn't able to find a way around this issue using a Windows Store Python version and resorted to installing it via the Python website. After that, Ghidrathon worked just fine. Please let me know if there's any other information I can provide, as it seems that any user(?) trying to use Python from the Windows Store would have this issue. |
First off, great work on the development and architecture of this plugin I'm looking forward to Ghidra + Python3 scripts!
I wanted to document my process on attempting to getting this plugin running:
Prerequisites notes
Python
Python 3.10 was installed through the Windows Store
i.e. installed to:
%LocalAppData%\Packages\PythonSoftwareFoundation.Python.3.10_...\
and therefore
pip --user install jep
installed to:%LocalAppData%\Packages\PythonSoftwareFoundation.Python.3.10_...\LocalCache\local-packages\Python310\site-packages\jep
Java
Eclipse Adoptium OpenJDK installed to:
C:\Program Files\Eclipse Adoptium\jdk-11.0.16.101-hotspot
with both
bin\client\jvm.dll
andbin\server\jvm.dll
Building
Build succeeded with a small deprecation warning, observable with this diff:
See: #9
And the Jep binaries were correctly discovered and bundled with the Ghidra plugin under
dist/
Installing
I get a Ghidra Exception on loading the plugin after a restart:
in investigating the
jep.dll
with ldd in git bash Thanks WindowsThere are two unreachable DLLs
jvm.dll
could not be found out of the Eclipse Adoptium OpenJDK install directory (or maybe not able to disambiguate between the two?)python310.dll
seems to not be distributed with the windows store build (perhaps a static build?)I understand that these are likely issues specific to Jep itself however I wanted to report general usability issues to either make more meaningful Ghidra error messages and to upstream these issues to Jep is called for.
Thanks again for the project!
Operating System: Windows 11 21H2 22000.856
Java Version: OpenJDK 11.0.16.1
Ghidra Version: 10.1.5
Gradle Version: 7.5.1
Python Version: 3.10.7
Jep Version: 4.0.3
The text was updated successfully, but these errors were encountered: