Ghidra: Import the actual source code to GitHub, including build instructions

Created on 6 Mar 2019  Â·  10Comments  Â·  Source: NationalSecurityAgency/ghidra

Is your feature request related to a problem? Please describe.
With the code drop on ghidra-sre.org, there is no obvious way to build Ghidra from source.

Describe the solution you'd like

  • Judging from the plugin examples, Ghidra uses Gradle, so it'd be cool to have the Gradle project on GitHub.
  • Upload the actual source code to GitHub, not just *-src.zip next to the *.jar files
  • Update the README with build instructions and a quick start

Describe alternatives you've considered
N/A

Additional context
N/A

Enhancement

Most helpful comment

The full source code is now available!

All 10 comments

This repository is a placeholder for the full open source release. Be assured efforts are under way to make the software available here. In the meantime, enjoy using Ghidra on your SRE efforts, developing your own scripts and plugins, and perusing the over a million lines of Java and Sleigh code released within the initial public release. The release can be downloaded from our project homepage. Please consider taking a look at our contributor guide to see how you can participate in this open source project when it becomes available.

Sounds like they're working on it. Note that one of the big pieces yet unrevealed is the source code for the decompiler.

Having a tracking bug seems like a good idea anyways. I'm glad they do this at all, I can't imagine the bureaucratic hurdles one has to jump through to make this happen.

Will the decompiler be open source eventually?

Per our FAQ, we are working diligently toward releasing the source repo. In the meantime, we're happy to have released the binary build with the Sleigh and Java source.

Do you have a rough timeframe as to when that may be? Are we looking at weeks or months do you think?

The full source code is now available!

Are there build instructions anywhere?

task CheckToolChain {
    // Native C/Cpp plugins will trigger failure if no tool chain found
    doFirst {
        if (org.gradle.internal.os.OperatingSystem.current().isWindows()) {

            project.ext.VISUAL_STUDIO_INSTALL_DIR = project.ext.VISUAL_STUDIO_BASE_DIR + "\\Preview"

The code above in nativeBuildProperties.gradle should also check for
Enterprise
Preview

and also check for VS2019

See discussion in
https://github.com/NationalSecurityAgency/ghidra/pull/730 regarding VS
support

On Wed, Sep 4, 2019 at 13:24 Roland Harrison notifications@github.com
wrote:

task CheckToolChain {
// Native C/Cpp plugins will trigger failure if no tool chain found
doFirst {
if (org.gradle.internal.os.OperatingSystem.current().isWindows()) {

      project.ext.VISUAL_STUDIO_INSTALL_DIR = project.ext.VISUAL_STUDIO_BASE_DIR + "\\Preview"

The code above in nativeBuildProperties.gradle should also check for
Enterprise
Preview

and also check for VS2019

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/NationalSecurityAgency/ghidra/issues/29?email_source=notifications&email_token=ABAPKN3DZHVPHDLGM564MVTQH5PEFA5CNFSM4G4BSKWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD52UBIA#issuecomment-527777952,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABAPKN4DGWTFB4QOHXMF4YTQH5PEFANCNFSM4G4BSKWA
.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lab313ru picture lab313ru  Â·  16Comments

yifanlu picture yifanlu  Â·  24Comments

ghost picture ghost  Â·  29Comments

SocraticBliss picture SocraticBliss  Â·  26Comments

dalvarezperez picture dalvarezperez  Â·  19Comments