As the GCC manual notes, "On most systems that use stabs format, -g
enables use of extra debugging information that only GDB can use;
this extra information makes debugging work better in GDB but will
probably make other debuggers crash or refuse to read the program."
-gstabs produces stabs without GDB extensions, and thus the AmigaOS
debugger will work.
The host targets for Android ARM builds are changed to "android-arm"
and "android-arm-v7a", from "android" and "android-v7a", and two new
targets are added of "android-mips" for MIPS and "android-x86" for
x86.
The older "android" and "android-v7a" targets are still supported,
but are deprecated.
This implements count badge, progress bar, and icon overlay.
It uses the NSDockTile API which is available since OS X 10.5.
The code compiles and run on older system but without doing
anything.
Formerly the taskbar support was *always* enabled except when the backend or
user specified that it should be disabled. This causes nasty crashes for
backends which do not have any taskbar support (like DC, Tizen and probably
more which simply did not disable it so far) when defaultErrorHandler was
called for example (Mass Add is also broken for those).
The SDL (and derived backends) worked around missing taskbar support by
simply faking a dummy taskbar implementation (but still claiming in configure
that we feature taskbar integration, ouch).
To avoid all non-SDL backends from manually specifying _taskbar=no I added
some auto detection code which simply only enables taskbar support in case
ScummVM is built on Win32 or libunity is present.
This changes makes ScummVM compilable with newer versions of DevKitPPC. ScummVM can be linked against the original libogc and libfat. That makes some newer WiiMotes work, improves audio-/video-playback and contains various improvements.
This caused an exception if a error() call occurs, rather than a
clean exit. This occurred in the defaultErrorHandler() function of
engines/engine.cpp, probably due to g_system->getTaskbarManager()
returning a null pointer.
This is mainly "cosmetic" to keep the SCUMM engine and subengines at
the top of the various files, but probably a good idea to prevent any
subtle regressions associated with changing the order.
Each engine now only has to provide a single configure.engine file
adding the engine into the configure script, which then produces the
required other files automatically.
This is the third and final commit enabling fully pluggable engines.
Now providing an engine folder contains a configure.engine, engine.mk
and engine-plugin.h file, it will be picked up automatically by the
configure script.
This is the first part of allowing engines to be added dynamically.
They are placed into a folder in engines/ which must contain a file
named "configure.engine" to add the engine, which is pulled into the
top level configure script automatically.
This was breaking AmigaOS4 builds for the porter as his libpng was built
as a shared library depending on zlib. This should be safe for static
builds as well.
Instead of always assuming /sw (i.e. fink) it should now also pick up
the macports prefix or /usr/local depending on which one exists.
Of course this can still be overwritten with --with-staticlib-prefix
These now restore the original release build logic to ensure that we
don't have issues with releases. Missing something here as _debug_build
doesn't seem to work as I expected...
After this change, release builds will still have serial debug disabled,
but debug builds will now not provide this unless --enable-debug is
passed explicitly. This could have been another option or environment
variable, but other embedded ports do similar things with _debug_build
and this looks like the cleanest way to deal with this.
This allows configure to work fine on Solaris 10 again. This fixes bug
#3614513 "A few posixisms have crept into configure (w/ patch)".
Thanks to lblume for his patch.
This fixes compatibility issues with clang when using -enable-Werror:
clang generates a warning when being passed both "-c" and linker-only
flags like "-L" or "-l". Combined with -Werror, this causes a spurious
configure failure.
