| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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 now generated automatically by the configure script from the
engine directory names.
|
|
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 second part of allowing engines to be added dynamically.
Each folder in engines/ which must contain a file named "engine.mk"
containing the make definitions for that engine.
|
|
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.
|
|
|
|
|
|
|
|
use it from actions.
|
|
|
|
|
|
list from end to beginning
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
16bit flag.
|
|
|
|
|
|
|
|
|
|
|
|
I personally used filters within my IDE, but since others are now joining the project,
it was brought to my attention that some better organization would be nice.
|
|
Also account ZNem and ZGI using different timer scales
|
|
This can be used to enable/disable Controls as well. Also, enabling/disabling
should be somewhat faster now as well as checking for enabled/disabled.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
engine.
|
|
|
