-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
does not support files in big endian [feature] [willing to help] #9
Comments
It's a duplicate of this issue: #7 I simply didn't have the time to add it in yet. I'd like to rework the codebase eventually into something a bit more split up and also go from a custom format to a JSON wherever possible. Nevertheless, adding in byteswaps to the file IO operations shouldn't be too hard. (Although I'm contemplating to also go from standard C file funcs to C++ fstream) But as it is right now, it does still work so it's not a big problem. All it needs is a shim for fread/fwrite that can byteswap AFAIR. Also no need for a explicit flag (except maybe for a forced read). It can be easily autodetected from the header magic as you can tell. Feel free to submit a pull request if you wanna add in byteswaps yourself. I can do the reworks later. |
I'm following the project with great interest. Hope to handle big endian files soon with this gerat tool |
I wrote some pretty overly-complex shit code a couple weeks ago but here it is. Completely untested. I identified already that adding fread and fwrite functions was the way to go. Feel free to gut it for me and gut me. endianess.h
endianess.cpp
told you |
@ifeelagood i have zero programming skills man :) |
@ifeelagood Bro could you add your code with the big endian support to exe file and send it to me? Would be awesome daniel.sul [at] hotmail.de |
The game in question is PS3/XB360 Skate 3
Bad header magic! Expected: 0x50464478, Got: 0x78444650
, which is clearly due to the generation of consoles being big endian.I suggest adding another flag to read in big endian.
I am willing to add this myself.
The text was updated successfully, but these errors were encountered: