Setting default parameter values at build time

[ricrpi]

When users run mupen64plus for the first time or if they delete their mupen64plus.cfg file then mupen64plus will auto-generate a new cfg file. This cfg file may not have default values that are compatible with some unofficial ports.

Users can of course change these, either on the command line, manually editing the file or copying in a good cfg file.

However for inexperienced users, perhaps a method to set these defaults at build time should be considered.

I would like to suggest that such a method used is similar to how COREDIR and PLUGINDIR are used within the makefile system. Then maintainers of unofficial ports could customize official plugin defaults from within their build scripts. (This would remove the need to fork and maintain updates where only these defaults are changed).

Note: This change would have to be applied to all mupen64plus repositories else an inexperienced user may still need to do something with the cfg file.

As a side note I would like to add that I have not seen many comments/questions about how to change the mupen64plus configuration on the raspberry Pi forums, given the aims of the device is to be educational and so has a higher proportion of inexperienced users of linux, I feel this 'Issue' is of low importance and more of an enhancement.

[krnlyng]

My Sailfish OS port would definitely benefit from such an option. Something along the lines:
DEFAULT_VIDEO_PLUGIN="mupen64plus-video-glide64mk2.so" make all -C projects/unix

or maybe (this would also allow setting special config parameters):
USE_DEFAULT_CONFIGURATION_FILE="/path/to/custom/mupen64plus.cfg" make all -C projects/unix

This would allow me to use the upstream mupen64plus-ui-console frontend without dirty hacks to get it going on my target devices...

If we agree upon a method, i would volunteer to implement it, if no one else does it :).