2022-09-08 21:19:20 +00:00
# objdiff [![Build Status]][actions]
[Build Status]: https://github.com/encounter/objdiff/actions/workflows/build.yaml/badge.svg
[actions]: https://github.com/encounter/objdiff/actions
2023-11-25 04:17:35 +00:00
A local diffing tool for decompilation projects. Inspired by [decomp.me ](https://decomp.me ) and [asm-differ ](https://github.com/simonlindholm/asm-differ ).
Features:
- Compare entire object files: functions and data.
- Built-in symbol demangling for C++.
- Automatic rebuild on source file changes.
- Project integration via [configuration file ](#configuration ).
- Search and filter all of a project's objects and quickly switch.
- Click to highlight all instances of values and registers.
2022-09-08 21:19:20 +00:00
2023-08-12 18:18:09 +00:00
Supports:
2022-09-08 21:19:20 +00:00
- PowerPC 750CL (GameCube & Wii)
2022-09-20 23:04:32 +00:00
- MIPS (Nintendo 64)
2022-09-08 21:19:20 +00:00
2023-08-12 18:18:09 +00:00
See [Usage ](#usage ) for more information.
2022-09-08 23:46:19 +00:00
![Symbol Screenshot ](assets/screen-symbols.png )
![Diff Screenshot ](assets/screen-diff.png )
2022-09-08 21:19:20 +00:00
2023-08-12 18:18:09 +00:00
## Usage
2023-08-12 18:41:19 +00:00
objdiff works by comparing two relocatable object files (`.o`). The objects are expected to have the same relative path
from the "target" and "base" directories.
2023-08-12 18:18:09 +00:00
2023-08-12 18:41:19 +00:00
For example, if the target ("expected") object is located at `build/asm/MetroTRK/mslsupp.o` and the base ("actual")
object is located at `build/src/MetroTRK/mslsupp.o` , the following configuration would be used:
2023-08-12 18:18:09 +00:00
- Target build directory: `build/asm`
- Base build directory: `build/src`
- Object: `MetroTRK/mslsupp.o`
objdiff will then execute the build system from the project directory to build both objects:
```sh
$ make build/asm/MetroTRK/mslsupp.o # Only if "Build target object" is enabled
$ make build/src/MetroTRK/mslsupp.o
```
The objects will then be compared and the results will be displayed in the UI.
See [Configuration ](#configuration ) for more information.
## Configuration
2023-08-12 18:41:19 +00:00
While **not required** (most settings can be specified in the UI), projects can add an `objdiff.json` (or
`objdiff.yaml` , `objdiff.yml` ) file to configure the tool automatically. The configuration file must be located in
the root project directory.
If your project has a generator script (e.g. `configure.py` ), it's recommended to generate the objdiff configuration
file as well. You can then add `objdiff.json` to your `.gitignore` to prevent it from being committed.
2023-08-12 18:18:09 +00:00
```json5
// objdiff.json
{
"custom_make": "ninja",
2023-09-03 13:28:22 +00:00
// Only required if objects use "path" instead of "target_path" and "base_path".
2023-08-12 18:41:19 +00:00
"target_dir": "build/asm",
"base_dir": "build/src",
2023-09-03 13:28:22 +00:00
2023-08-12 18:18:09 +00:00
"build_target": true,
"watch_patterns": [
"*.c",
"*.cp",
"*.cpp",
"*.h",
"*.hpp",
"*.py"
],
"objects": [
{
2023-09-03 13:28:22 +00:00
"name": "main/MetroTRK/mslsupp",
// Option 1: Relative to target_dir and base_dir
2023-08-12 18:18:09 +00:00
"path": "MetroTRK/mslsupp.o",
2023-09-03 13:28:22 +00:00
// Option 2: Explicit paths from project root
// Useful for more complex directory layouts
"target_path": "build/asm/MetroTRK/mslsupp.o",
"base_path": "build/src/MetroTRK/mslsupp.o",
2023-08-12 18:18:09 +00:00
"reverse_fn_order": false
},
// ...
]
}
```
2023-09-03 13:28:22 +00:00
`custom_make` _(optional)_ : By default, objdiff will use `make` to build the project.
If the project uses a different build system (e.g. `ninja` ), specify it here.
`target_dir` _(optional)_ : Relative from the root of the project, this where the "target" or "expected" objects are located.
These are the **intended result** of the match.
`base_dir` _(optional)_ : Relative from the root of the project, this is where the "base" or "actual" objects are located.
These are objects built from the **current source code** .
`build_target` : If true, objdiff will tell the build system to build the target objects before diffing (e.g.
2023-08-12 18:41:19 +00:00
`make path/to/target.o` ).
2023-09-03 13:28:22 +00:00
This is useful if the target objects are not built by default or can change based on project configuration or edits
to assembly files.
Requires the build system to be configured properly.
`watch_patterns` _(optional)_ : A list of glob patterns to watch for changes.
([Supported syntax](https://docs.rs/globset/latest/globset/#syntax))
If any of these files change, objdiff will automatically rebuild the objects and re-compare them.
If not specified, objdiff will use the default patterns listed above.
`objects` _(optional)_ : If specified, objdiff will display a list of objects in the sidebar for easy navigation.
> `name` _(optional)_: The name of the object in the UI. If not specified, the object's `path` will be used.
>
> `path`: Relative path to the object from the `target_dir` and `base_dir`.
> Requires `target_dir` and `base_dir` to be specified.
>
> `target_path`: Path to the target object from the project root.
> Required if `path` is not specified.
>
> `base_path`: Path to the base object from the project root.
> Required if `path` is not specified.
>
> `reverse_fn_order` _(optional)_: Displays function symbols in reversed order.
Used to support MWCC's `-inline deferred` option, which reverses the order of functions in the object file.
2023-11-28 00:52:12 +00:00
## Building
2023-09-03 13:28:22 +00:00
2023-11-28 00:52:12 +00:00
Install Rust via [rustup ](https://rustup.rs ).
```shell
$ git clone https://github.com/encounter/objdiff.git
$ cd objdiff
$ cargo run --release
# or, for wgpu backend (recommended on macOS)
$ cargo run --release --features wgpu
```
2023-08-12 18:18:09 +00:00
## License
2022-09-08 21:19:20 +00:00
Licensed under either of
* Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
* MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)
at your option.
### Contribution
2023-08-12 18:41:19 +00:00
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as
defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.