ghidra/DevGuide.md

297 lines
8.9 KiB
Markdown
Raw Normal View History

2019-03-26 17:45:32 +00:00
# Developer's Guide: Getting Started
Install OpenJDK 11 and make sure it's the default java.
2019-03-26 21:58:40 +00:00
Install a version of Eclipse with good support for Java 11.
Eclipse 2018-12 or later should work.
2019-03-26 17:45:32 +00:00
Technically, you can launch with any JRE/JDK, but it's up to you ensure OpenJDK 11 is properly configured in Eclipse.
2019-03-26 21:58:40 +00:00
Install Gradle 5.0, add it to your `PATH`, and ensure it is launched using OpenJDK 11.
Other versions of Gradle may work, but they have not been tested.
2019-03-26 17:45:32 +00:00
## Setup Repositories
Of course, you may choose any directory for your working copy, but these instructions will assume you have cloned the repo to `~/git`.
Be sure to adjust the commands to match your chosen working directory if different than suggested:
```bash
cd ~/git
git clone git@github.com:NationalSecurityAgency/ghidra.git
```
Ghidra's build uses artifact named as available in Maven Central and Bintray JCenter, when possible.
Unfortunately, in some cases, the artifact or the particular version we desire is not available.
So, in addition to mavenCentral and jcenter, you must configure a flatDir-style repository for manually-downloaded dependencies.
Create `~/.gradle/init.d/repos.gradle` with the following contents:
```groovy
ext.HOME = System.getProperty('user.home')
allprojects {
repositories {
mavenCentral()
jcenter()
flatDir name:'flat', dirs:["$HOME/flatRepo"]
}
}
```
You should also create the `~/flatRepo` folder to hold the manually-downloaded dependencies:
```bash
mkdir ~/flatRepo
```
If you prefer not to modify your user-wide Gradle configuration, you may use
Gradle's other init script facilities, but you're on your own.
## Get Dependencies for FileFormats:
Download `dex-tools-2.0.zip` from the dex2jar project's releases page on GitHub.
Unpack the `dex-*.jar` files from the `lib` directory to `~/flatRepo`:
```bash
cd ~/Downloads # Or wherever
curl -OL https://github.com/pxb1988/dex2jar/releases/download/2.0/dex-tools-2.0.zip
unzip dex-tools-2.0.zip
cp dex2jar-2.0/lib/dex-*.jar ~/flatRepo/
```
Download `AXMLPrinter2.jar` from the "android4me" archive on code.google.com.
Place it in `~/flatRepo`:
```bash
cd ~/flatRepo
curl -OL https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/android4me/AXMLPrinter2.jar
```
## Get Dependencies for DMG:
Download `hfsexplorer-0_21-bin.zip` from www.catacombae.org.
Unpack the `lib` directory to `~/flatRepo.`:
```bash
cd ~/Downloads # Or wherever
curl -OL https://sourceforge.net/projects/catacombae/files/HFSExplorer/0.21/hfsexplorer-0_21-bin.zip
mkdir hfsx
cd hfsx
unzip ../hfsexplorer-0_21-bin.zip
cd lib
cp csframework.jar hfsx_dmglib.jar hfsx.jar iharder-base64.jar ~/flatRepo/
```
## Import Gradle Project
2019-03-26 21:58:40 +00:00
If you want just to build Ghidra, you may skip ahead to Building Ghidra.
Import Ghidra into Eclipse using the integrated BuildShip plugin.
Be sure to select Gradle 5.0, or point it at your local installation.
Other IDEs should work, but we have not tested with them.
2019-03-26 17:45:32 +00:00
You may see build path errors until the environment is properly prepared, as described below.
2019-03-26 21:58:40 +00:00
*Alternatively*, you may have Gradle generate the Eclipse projects (`gradle eclipse`) and import those instead.
This is the way to go if you'd prefer not to activate Gradle's BuildShip plugin.
2019-03-26 17:45:32 +00:00
## Prepare the Environment
From the project root, execute:
```bash
2019-03-26 21:58:40 +00:00
gradle prepDev -x yajswDevUnpack
2019-03-26 17:45:32 +00:00
```
2019-03-26 21:58:40 +00:00
The `prepDev` tasks primarily include generating some source, indexing our online help, and unpacking some dependencies.
Regarding `yajswDevUnpack`, please see the relevant sections on GhidraServer below.
For now, we exclude the unpack task.
2019-03-26 17:45:32 +00:00
Optionally, to pre-compile all the language modules, you may also execute:
```bash
2019-03-26 21:58:40 +00:00
gradle sleighCompile
2019-03-26 17:45:32 +00:00
```
Refresh the Gradle project in Eclipse.
You should not see any errors at this point, and you can accomplish many development tasks.
However, some features of Ghidra will not be functional until further steps are taken.
### Building the natives
Some of Ghidra's components are built for the native platform.
We currently support Linux, macOS, and Windows 64-bit x86 systems.
Others should be possible, but we do not support them.
#### decompile
Install bison and flex.
Now build using Gradle:
On Linux:
```bash
2019-03-26 21:58:40 +00:00
gradle decompileLinux64Executable
2019-03-26 17:45:32 +00:00
```
On macOS:
```bash
2019-03-26 21:58:40 +00:00
gradle decompileOsx64Executable
2019-03-26 17:45:32 +00:00
```
On Windows:
```cmd
gradlew decompileWin64Executable
```
#### demangler_gnu
Build using Gradle:
On Linux:
```bash
2019-03-26 21:58:40 +00:00
gradle demangler_gnuLinux64Executable
2019-03-26 17:45:32 +00:00
```
On macOS:
```bash
2019-03-26 21:58:40 +00:00
gradle demangler_gnuOsx64Executable
2019-03-26 17:45:32 +00:00
```
On Windows:
```cmd
gradlew demangler_gnuWin64Executable
```
#### sleigh
2019-03-26 21:58:40 +00:00
The sleigh compiler has been ported to Java and integrated with Ghidra.
The native sleigh compiler may still be useful for those who'd like quicker feedback by compiling from the command line.
To build the native sleigh compiler, install bison and flex.
2019-03-26 17:45:32 +00:00
Now, use Gradle:
On Linux:
```bash
2019-03-26 21:58:40 +00:00
gradle sleighLinux64Executable
2019-03-26 17:45:32 +00:00
```
On macOS:
```bash
2019-03-26 21:58:40 +00:00
gradle sleighOsx64Executable
2019-03-26 17:45:32 +00:00
```
On Windows:
```cmd
gradlew sleighWin64Executable
```
2019-03-26 21:58:40 +00:00
## Run Ghidra from Eclipse
2019-03-26 17:45:32 +00:00
2019-03-26 21:58:40 +00:00
To run or debug Ghidra from Eclipse, use the provided launcher.
2019-03-26 17:45:32 +00:00
2019-03-26 21:58:40 +00:00
# Building Ghidra
2019-03-26 17:45:32 +00:00
2019-03-26 21:58:40 +00:00
To build the full Ghidra distribution, you must also build the GhidraServer.
2019-03-26 17:45:32 +00:00
2019-03-26 21:58:40 +00:00
## Get Dependencies for GhidraServer
2019-03-26 17:45:32 +00:00
Building the GhidraServer requires "Yet another Java service wrapper" (yajsw) version 12.12.
Note that building the full Ghidra package requires building the GhidraServer.
Download `yajsw-stable-12.12.zip` from their project on www.sourceforge.net, and place it in a directory named:
`ghidra.bin/Ghidra/Features/GhidraSerer/`:
```bash
cd ~/Downloads # Or wherever
curl -OL https://sourceforge.net/projects/yajsw/files/yajsw/yajsw-stable-12.12/yajsw-stable-12.12.zip
mkdir -p ~/git/ghidra.bin/Ghidra/Features/GhidraServer/
cp ~/Downloads/yajsw-stable-12.12.zip ~/git/ghidra.bin/Ghidra/Features/GhidraServer/
```
Use Gradle to unpack the wrapper for development.
From your clone:
```bash
2019-03-26 21:58:40 +00:00
gradle yajswDevUnpack
2019-03-26 17:45:32 +00:00
```
2019-03-26 21:58:40 +00:00
## Building the Package
2019-03-26 17:45:32 +00:00
Before building, you may want to update the version and release name.
These properties are kept in `Ghidra/application.properties`.
If you want it included, you must also build the GhidraDevPlugin module first.
2019-03-26 21:58:40 +00:00
Some supporting data will also be missing.
See the sections below for instructions to produce these components.
You may also be able to copy some of this data from a previous official distribution.
2019-03-26 17:45:32 +00:00
To build the full package, use Gradle:
```bash
2019-03-26 21:58:40 +00:00
gradle buildGhidra
2019-03-26 17:45:32 +00:00
```
The output will be placed in `build/dist/`.
It will be named according to the version, release name, build date, and platform.
To test it, unzip it where you like, and execute `./ghidraRun`.
# Building Supporting Data
Some features of Ghidra require the curation of rather extensive data bases.
These include the Data Type Archives and Function ID Databases, both of which require collecting header files and libraries for the relevant SDKs and platforms.
Much of this work is done by hand, and the results are simply copied into the build.
We intend to document these procedures as soon as we can.
In the meantime, those artifacts can always be extracted from our binary release.
## Building Data Type Archives
TODO
## Building FID Databases
TODO
2019-03-26 21:58:40 +00:00
# Developing / Building the GhidraDev Plugin
First, install the Eclipse Plugin Development Environment (PDE).
By default, the GhidraDev project is excluded from the build.
To enable it, uncomment it in `settings.gradle`.
You will need some additional runtime dependencies:
## Get Dependencies for GhidraDev
Building the GhidraDev plugin for Eclipse requires the CDT and PyDev plugins for Eclipse.
Download `cdt-8.6.0.zip` from The Eclipse Foundation, and place it in a directory named:
`ghidra.bin/GhidraBuild/EclipsePlugins/GhidraDev/buildDependencies/`.
`ghidra.bin` must be a sibling of `ghidra`.
To respect the CDT project's resources, you will need to download the file using a browser, or at the very least, locate a suitable mirror on your own:
```bash
cd ~/Downloads # Or wherever
curl -OL https://$CHOOSE_YOUR_MIRROR/pub/eclipse/tools/cdt/releases/8.6/cdt-8.6.0.zip
mkdir -p ~/git/ghidra.bin/GhidraBuild/EclipsePlugins/GhidraDev/buildDependencies/
cp ~/Downloads/cdt-8.6.0.zip ~/git/ghidra.bin/GhidraBuild/EclipsePlugins/GhidraDev/buildDependencies/
```
Download `PyDev 6.3.1.zip` from www.pydev.org, and place it in the same directory:
```bash
cd ~/Downloads # Or wherever
curl -OL https://sourceforge.net/projects/pydev/files/pydev/PyDev%206.3.1/PyDev%206.3.1.zip
cp ~/Downloads/'PyDev 6.3.1.zip' ~/git/ghidra.bin/GhidraBuild/EclipsePlugins/GhidraDev/buildDependencies/
```
Use Gradle to unpack the dependencies.
Note that these tasks will not work until you enable the GhidraDev project in `settings.gradle`.
From your clone:
```bash
gradle cdtUnpack pyDevUnpack
```
## Import the GhidraDev Project
If you're using BuildShip, simply refresh the Gradle project in Eclipse.
If you're not using BuildShip, re-run `gradle eclipse` and import the new project.