The -hlevideo plugin was just a quick hack to provide the functionality to
enable the DisplayListToGraphicsPlugin option. This is not the behavior
encouraged by mupen64plus-core because it already provides a configuration
system.
New configuration options are:
* DisplayListToGraphicsPlugin
Send display lists to the graphics plugin (hlevideo)
* AudioListToAudioPlugin
Send audio lists to the audio plugin
* WaitForCPUHost
Force CPU-RSP signals synchronization
* SupportCPUSemaphoreLock
Support CPU-RSP semaphore lock
The builds from the original author used SSSE3 in their default build but it
seems it is only supported by fairly recent Intel processors. Thus setting it
to SSE2 instead by default should be better for people building it from source.
The default builds by the original author of the plugin were optimized for
SSSE3 or SSE2. These build options were missing in this port. Both can now be
build by setting the make parameter SSE to either SSE2 or SSSE3. It can also be
set to none when no SSE optimizations should be activated by the Makefile (own
FLAGS can still be supplied using CFLAGS).
Both build will get an own postfix in the future but currently the postfix is
used by the HLEVIDEO compile option. The postfix will be activated when the
HLEVIDEO configuration is done through the mupen64plus configuration system.
The 3DNow! instruction set is not supported by Intel processors.
Although gcc will not likely emit 3DNow! instructions, it is
dangerous to permit 3DNow! instructions due to the fact that Intel
has never supported 3DNow! instructions.
The *.d depends files for make just list the files used when building an object
file. Removing a file listed in such a dependency file causes make to search
for a way to recreate it. This usually cannot work because these files aren't
autogenerated.
The gcc option -MP can be used to generate empty rule for these files. Removing
a file in a dependency list will then execute this empty rule and continue with
the execution of the creation of the object file. This compilation process will
then automatically correct the dependency file.
The GCC manual states for different parameters that the options for compilation
must also be used when linking. The options for compilation are stored in
CFLAGS and added to LINK.o to fix the behavior.
Option which need this are for example -fPIC/-fPIE or -flto.