This allows an initial/default configuration file to be specified via the command line. This allows a default settings file to be bundled and loaded even if it's installed to a read-only location, such as Program Files on Windows, and allows the written config file to be deleted without losing the custom defaults.
Place file named 'scummvm=autorun' next to the ScummVM.
If the file is empty, scummvm will run in autodetect mode, basically
as './scummvm -p . --auto-detect'.
If the file is not empty, then command line parameters will be read
from it one per line. Empty lines and lines starting from '#' are ignored.
If the user supplies more parameters at the command line, those
will also be used and will override the parameters from the autorun file.
Rename scummvm executable into 'scummvm-auto*' and it is equivalent
of 'scummvm -p . --auto-run'. All additional arguments on the command
line are also processed and override the automatic arguments.
This was not properly implemented in GCC versions before 5.1, and
we still have some ports using older GCC versions.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43453#c7 and commit
6ac3994e3e582ec6a304c2a566bb1b0c69d507d2.
This allows to save some space on constrained devices which still allow
for command line.
Enable this space saving on DS and enable back command line support.
Cleanup old workaround for 3DS.
This is used by 3D games to limit the frames per seconds.
The default value was lost in commit b586571900 when sync'ing
ScummVM and ResidualVM code. This resulting in a default of 0,
which means no throtling.
This should fix bug #13631
Follow-up to the feature that allows skipping certain ADGF flags.
This here now also allows skipping of incomplete file/md5/size matches. It is basically the same behavior as the graylist. For the mass add all files are treated as if they are on the list.
I added skipping for the ADGF_WARNING and ADGF_UNSUPPORTED flags.
For me, this is mostly about fixing bug no. 13282. We sometimes have bogus entries which only have the purpose of presenting the error message (reasons for being unsupported) contained in the extra field of the detection entry.
The SDL backend was getting that path at the start and storing
it in a class member so that it would persist for the session.
But now that we have a kSessionDomain in ConfMan, it is cleaner
to use that (and this will also work for non-SDL backends).
