Ramblings about hobbyist game development
– make things compatible with current libglm releases
– make olives compile and run with recent libvulkan releases (WiP, breakage occurring still)
– fewer magic numbers
Maintenance changes, before that I was forced to downgrade to older versions of both in order to make OLives compile. Not a fun change, at all. 🙁
This is the first in a series of maintenance commits before going back to more feature driven development.
add the script to the objects themselves and use it in a proof-of-concept type of way when selecting a human
Further integrate the loaded script by moving the script instances from the ObjectType to the actual Objects. This way we can actually interact with the instantiated Python module, meaning we have the first more or less meaningful interaction between the Python and C++ parts:
update .gitignore
It makes sense not to have precompiled Python bytecode in the repository.
– add a (one way) binding from C++ to python for the time being
– automatically load scripts on a per object type basis
– add the ability to have optional configuration settings
This marks the introduction of Python by using pybind.
At this point it is not doing much except for laying groundwork for what is to come: adding new properties to the Object and ObjectType classes and extending the ObjectType configuration to define a script file that needs to be loaded when an Object is added to the GameState.
Right now, a script file is being loaded and a script interpreter instance is being instantiated when an object is being created and this is where the integration ends: no Python code is actually executed at this point.
The single Python file currently loaded looks like this:
It is relatively easy to tell where this is going by looking at the function names, but as mentioned before, so far the only important thing is that this is a syntactically correct Python file.