You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For debugging stuff (like ASE/ACE and other setups), it'd be easiest to import the entire codebase in MWCW from a .mcp file, and then run it on the ISNE. However, currently when adding all the .s and .c files, as well as the .lcf files, it doesn't want to build. Hence if we are able to create a valid .mcp file once we're done with decomp, this allows for way easier debugging @Martmists-GH can you please elaborate on this further? Is this still necessary?
The basic idea is to be able to use the official debugger and devkit to step-by-step debug the code, rather than having to figure out the currently loaded overlays, code (re-)location, etc.
While not 100% necessary, this was one of the goals I had in mind when creating this project, as it would make debugging ACE setups easier.
No description provided.
The text was updated successfully, but these errors were encountered: