"Proper" way to build Ghidra while iterating small changes? #7038
Replies: 1 comment 8 replies
-
|
If you want to do fast iterative development in the java code, i recommend you follow our instructions for setting up Eclipse. That's how the team develops. |
Beta Was this translation helpful? Give feedback.
-
|
When you say you have a Ghidra build, what do you mean? When developing out of eclipse, there is just the git repo...there shouldn't be another "build" somewhere. |
Beta Was this translation helpful? Give feedback.
-
|
How are you launching Ghidra in this scenario? |
Beta Was this translation helpful? Give feedback.
-
Yes. When I was working on extensions I was switching between VS Code and Eclipse but now trying to work on the main repo I'm just trying to do it in Eclipse so far. |
Beta Was this translation helpful? Give feedback.
-
I mean the app built successfully with gradle between just cloning the repo and trying to add some code changes. |
Beta Was this translation helpful? Give feedback.
-
From the debug icon and choosing "Ghidra". |
Beta Was this translation helpful? Give feedback.
-
I'm an old programmer who barely ever touched Java, now doing some Ghidra programming for fun.
I know learning how to use Java "properly" is a gigantic rabbithole so I just want to ask if I'm building it the right way or if there's something much smaller and faster I should be using?
Last week I downloaded the source and built it for the first time while doing other things and it worked fine. Then I put it away until today. Today I changed the name of one function to see how many errors would show up and built it the same way as last time, which I found on the Internet somewhere:
I was expecting it to be much fast since all the setup was done and a first build was done. It's on an external hard drive of my M1 MacBook Air. It took just over 20 minutes!
Can I do anything to make this fast enough to iterate experimental code changes?
Beta Was this translation helpful? Give feedback.
All reactions