New Implementation: mGBA

[mid-kid]

An old, linux-only implementation for mGBA was made here: https://github.com/mid-kid/mgba
This is of course, incomplete, and should be re-done, to fit better with the mGBA codebase, and support more platforms.

What is interesting about porting to mGBA, is that mGBA supports both GB and GBA games, and we can integrate it right in the emulator, making it the perfect option for the casual player that wants to get up and running. I presume this will become the primary non-development implementation in due time.

Ideally, this would also work on the other platforms that mGBA supports, but that should probably be a separate issue, given mGBA's structure.

[arves100]

https://github.com/arves100/mgba/tree/feature/adapter
Implemented here, apart from the missing issues (the fork should be transferred to reon directly), the current license of libmobile would not allow a merge (it would relicense all mgba code to agplv3), an idea would be splitting arduino and libmobile repo.

[mid-kid]

I'll relicense it when I'm done with the wip branch, don't worry about that. I chose AGPL mostly due to that being my default for hw projects, but I realize that's not a good license for a library.

[mid-kid]

@endrift Is MPL acceptable?

[endrift]

LGPL would be better for libmobile I think. MPL is...well, for libraries it's kinda meaningless.

[endrift]

That said, it depends on what you hope to accomplish with the license. If you don't care how people use it beyond attribution then MIT or BSD 2-clause would be better. If you want proper attribution and copyleft-like for the library, LGPL is better.

[mid-kid]

Thanks for the insight. I mostly care about getting back improvements, and due to frequent ABI changes, I intend this library to be shipped along with a project (which in practical terms often implies static linkage), so I feel like LGPL might hamper its adoption. That said, I mostly care about mGBA, so if LGPL is acceptable for that, I'll probably use that.

[endrift]

For static linking LGPL could hamper its adoption, since it requires statically linked programs to give a way to re-link with different versions of the library. This is rarely enforced, however, and is frequently violated. Either one works with mGBA since I'd probably vendor it upstream (unless I finally cave and use submodules).