| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fix wrong call in
|
|
|
|
|
|
RFC: Pluggable Engines #2 (No Python, just evolution of current configure shell and make code)
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The sequence loading helper should already check if the sequence is loaded and clean up the instance if not
|
|
(CID1004167)
|
|
|
|
|
|
|
|
|
|
|
|
- Rename existing function to load the last saved game
- Remove loadgame debugger command
|
|
- Check for valid stream in readValue/writeValue functions
- Properly initialize/clear members
|
|
|
|
|
|
|
|
|
|
|
