Skip to content

libretro port #59

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

Open
barbudreadmon opened this issue May 27, 2019 · 7 comments
Open

libretro port #59

barbudreadmon opened this issue May 27, 2019 · 7 comments

Comments

@barbudreadmon
Copy link

That's not a request, i discovered your emulator after your message about FBNeo today, and i just wanted to mention that if you are interested in a libretro port, i can probably help you with that :).

@snickerbockers
Copy link
Member

Yes, I'd very much appreciate your help with that!

The same IRL thing which prevents me from getting to work on the FBNeo stuff for a couple weeks is also going to keep me from making progress on WashingtonDC so I won't be around to coordinate with you for a while.

The general gist of things is that all the core emulation code is in a library called libwashdc, and the frontend code is in a program called washingtondc which links against libwashdc. So hopefully, if I've done it right then it should be possible to create a libretro core without making invasive changes to the emulator by having the core link against libwashdc and use the same APIs to control execution that washingtondc uses.

Like I said, I'll be gone for a month or two, so I'll let you know when I'm back. Or if you want you can get started now (but don't feel pressured to do so!).

Thanks again!

@snickerbockers snickerbockers pinned this issue May 30, 2019
@barbudreadmon
Copy link
Author

I'll probably start working on it soon, thanks for the explanations :)

@snickerbockers
Copy link
Member

btw, the thing i was talking about that was going to keep me out of contact for a month or two turned out to not be as big of a deal as i had initially feared, so I'm able to talk about this now if you have any questions about how to implement or suggestions about things I need to change to accommodate it. I'm also going to start looking into the FB stuff soon, too.

@barbudreadmon
Copy link
Author

That's great news !
I didn't have time to look at the source code yet (i spent my free time this week working with address sanitizer on FBNeo). If anything, i would expect having troubles if the gl rendering is done by a sub thread, is that the case ?

It will be my first time writing a libretro port from scratch, but at this point i'm kinda used to the libretro api (i'm already working on several cores, including a few GL ones)

@snickerbockers
Copy link
Member

No, the GL rendering is done in the same thread as the emulation is.

@barbudreadmon
Copy link
Author

I started working on this yesterday, maybe you'll want to take a look : https://github.com/barbudreadmon/washingtondc/tree/master/src/libretro
I added a bunch of comment in libretro.cpp about what i still need to do.

@snickerbockers
Copy link
Member

okay, thanks. ill make sure to go into washingtondc's core code and fix it up to make it more versatile, too. seeing this made me realize there's some hardcoded config things that still need to be exposed via APIs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants