I can now build what (appears to be) a working S3&K rom. I need to do some more testing to make sure it's byte-accurate, but a quick play through of Angel Island showed everything looking normal. Changes I had to make:
- Fix and build an AS binary for OSX. Mostly resolving it's wonky strcpy replacement.
- Builld an s3p2bin binary for OSX. Worked without changes, so kudos to whoever wrote that in the first place.
- Knock up a replacement build script (works, but needs refinement).
- Alter the .asm files to use forward slashes in file paths rather than backwards slashes.
1. Are people interested in having this added to the community SVN? What's the best way of going about this? Assuming I've got commit permissions I could add it in a branch and someone could give it a sanity check before moving it into trunk.
2. Is it worth having my modified source for AS included in SVN as well? Not sure if this is helpful or not myself.
3. While I'm making changes I'd like to rearrange the build scripts so they're separate from the source files, and have output files in a separate dir as well. Has anyone got any thoughts on this?
4. Is anyone else hacking on OSX? Just wondering what kind of setup other people have got.