Mupen64plus 2.0 support for cxd4/rsp

[Sven Eckelmann]

Hi,

I was asked by mudlord on IRC to port your LLE RSP to mupen64plus. I actually
would like to avoid a special fork which has to sync all the time.
Nevertheless, I fulfilled his request using a minimal (as in quick hack)
port[1]. My question would be now: What would you allow in your repo and what
not?
Should this plugin be be zilmar RSP 1.1 spec + Win32 only or are you also
interested in adding Linux/BSD/.. or even M64P 2.0 support? Would you allow
project files for m64p or not?

Kind regards,
Sven

[1] https://bitbucket.org/ecsv/mupen64plus-rsp-cx4d/commits/all

[Sven Eckelmann]

On Tuesday 16 April 2013 12:21:19 RJ  wrote:
> Hello,
>
> I'm not sure if I can reply there on Google Code/Groups.
> I'm not even sure if I should be attempting to answer in this manner.

You can write to the Google group of mupen64plus as normal and mails get
approved by Richard. So, Cc'ing the mailing list would have been nice, but now
the mail was already out ;)

> But the answer to all of these questions is simple.
> My release of the source is effectively in to the public domain.

I know about the "license" but was more about getting the stuff together in
one repo to avoid splitted development. I personally love it when everything
gets together at the end and not everyone does its own stuff with it and at
the end the original author isn't able to see the improvements in one place.
But some of the things are now in your repo and this makes me at least a
little bit happy (not really how you applied the patches, but this is a
different topic and not so important).

> I have tried hard to make it as portable as possible for anyone's purposes.
> While I did not approve of mudlord's request to you, I am happy that you
> have managed to get it working with a minimal set of changes.
> I did not intend the plugin to be Win32-only.
> That was just the native template that zilmar's plugin specifications were
> embedded with, so I, to a controlled degree, defaulted to them.

> I did manually pull in some of the portability changes you added, but I do
> not wish to add API-specific code (either for M64 or anything else) to my
> repo. I wish to keep it neutral to the desires of future vendors.

OK, its fine. Thanks anyway for checking

> Lastly, you may find that my updates to cxd4/rsp will be a lot less frequent
> now that I have finally did a public release of the plugin and await
> tester-provoked changes, so you might not have to worry as much about
> keeping them in sync (although I could be wrong).

Let's see what the future brings. I personally hadn't much time to check it
out in detail.

Kind regards,
Sven