From 35c88445293b5930b0abaac8cc7d7659ff71642e Mon Sep 17 00:00:00 2001 From: KeybadeBlox Date: Wed, 4 Feb 2026 20:01:06 -0500 Subject: [PATCH] Move everything else to ghidra/ directory The only stuff left in delink/ was also for using with Ghidra, so we may as well also put it in ghidra/. --- documentation/gettingstarted.md | 14 +++++++------- {delink => ghidra}/delink.sh | 0 {delink => ghidra}/objects.csv | 0 3 files changed, 7 insertions(+), 7 deletions(-) rename {delink => ghidra}/delink.sh (100%) rename {delink => ghidra}/objects.csv (100%) diff --git a/documentation/gettingstarted.md b/documentation/gettingstarted.md index 5767e38..a198419 100644 --- a/documentation/gettingstarted.md +++ b/documentation/gettingstarted.md @@ -112,7 +112,7 @@ object files for objdiff. ### Producing Object Files Close all of your Ghidra windows and open a Unix-style shell (e.g. Git Bash if -on Windows) in the decompilation repository's `delink/` directory. The +on Windows) in the decompilation repository's `ghidra/` directory. The `delink.sh` script is our automated tool for extracting all the object files that have been identified so far. Invoke it with three arguments: @@ -214,12 +214,12 @@ request to merge it back into the online copy. ## Contributing to Delinking Getting the JSRF binary delinked is just as important as decompiling the resulting object files, but takes a bit more investment. The concrete task of -a delinking contributor is to populate `symboltable.tsv` in the `ghidra/` -directory and `objects.csv` in the `delink/` directory, which together enable -consistent delinking of object files. The former lists symbols at different -addresses through the whole executable, while the latter lists the address -ranges that have been identified as separable objects. Both of these things -are figured out by combing over the whole executable in Ghidra. +a delinking contributor is to populate `symboltable.tsv` and `objects.csv` in +the `ghidra/` directory, which together enable consistent delinking of object +files. The former lists symbols at different addresses through the whole +executable, while the latter lists the address ranges that have been identified +as separable objects. Both of these things are figured out by combing over the +whole executable in Ghidra. ### Updating `symboltable.tsv` diff --git a/delink/delink.sh b/ghidra/delink.sh similarity index 100% rename from delink/delink.sh rename to ghidra/delink.sh diff --git a/delink/objects.csv b/ghidra/objects.csv similarity index 100% rename from delink/objects.csv rename to ghidra/objects.csv