That's great. But how should I structure my sources? For now, they have the mupen64plus structure, and I planned to create a git with that structure. Will it be ok for you?I'll be working the Open Pandora project into our repository once it is public. This will probably prompt some restructuring of our folders (that is one of the reasons I've been wanting to incorporate an Open Pandora port - to help keep our repository more in-line with upstream Mupen64Plus). I'll be releasing updates along with the Android updates when the logistics are worked out, and pull in fixes from these other projects when there is anything useful.If you could structure it as a git fork of their repo, you can then get their future core updates "for free" by just doing "git pull". If you can put it on a public git so I can clone and build it for pandora, I could probably take a stab at some dynarec bugs too (eventually, not right now as I'm busy).Ok, I'll check and try to integrate their core update.
I just hope it doesn't end up with what we had with 1.x, with lots of tarbals all over the net, and where the source more or less got lost over time..