Windows .MMM files behave different than there mac counterparts.
The Director engine doesn't load the sprite surface, i.e.
it makes it a nullpointer. The surface is needed later on to
draw the files.
In commit dce6b012 we added the LDFLAGS, which were modified by the
configure script, to the linker stage of the plugins. Doing so turns
out not to work well for all system architectures.
This approach uses the unmodified LDFLAGS, stored in the SAVED_LDFLAGS
variable by the configure script, from the system environment for
linking dynamic plugins, which is very likely not to cause any harm.
Without an explicit size the layout system does not have enough
constraints to produce nice looking dialogs. Up until now the workaround
was to set explicit an size for some of the widget. This worked well
enough except when resizing down the window up until the widget size
constraints could no longer be enforced. At that point, produced layouts
looked too squished.
In the previous commit we modified the configure script to silently
ignore some options, that are not needed for ScummVM, but are valid
for the configure script generated by GNU Autotools, so the configure
macro for RPM-based distributions can be used when building a rpm
package for them.
Unfortunately the configure script, as used by ScummVM uses the --host
option to determine the target system it will actually be build for.
Autotools based configure scripts have a --target option for such a
purpose, and use the --host option to determine the system the build
is performed on.
For that reason there should be a way to discard the parameters passed
to the configure script with the --host option. The easiest approach
to achieve this goal, is to have an environment variable, which when
set influences the configure script to ignore the parameters of the
--host option.
Thus we introduced a variable called 'CONFIGURE_NO_HOST', that will
when set to anything, but an empty value, before invoking the configure
script, have the parameters of the --host option take no influence on
the configure stage (and the build stage as well).
RPM-based distributions come with a configure macro, that sets up the
whole build environment. In order to be able to use this macro, some
options, which are valid for the configure script generated by GNU
Autotools, should not error-out when preparing the build stage.
Some distributions populate their build environment with special
linker flags, e.g. for hardening purposes such as immediate binding
and/or read-only relocations.
Those flags should be honored when linking dynamic libraries.
