Need to add a test to run after build action to ensure dynamic linking is working correctly

[maiself]

Need to add a test to run after build action to ensure dynamic linking is working correctly. Breaking dynamic linking for any platform is blocking for any change.

• Add a small loader executable or somehow being Godot into the test?
• Need to add to workflow (I don't have experience with this)
• Must run for all platforms
• Must find and load libgodot-python from a location that is not cwd
• Must find and load included libpython (not ever system python)
• Python must be able to find the included stdlib (not system)
• Python must be able to load any native extension modules
• Native extension modules must be able to find dynamic symbols exported by the loaded libpython
• Native extension modules included with Python as well as third party modules (such as numpy) must be supported

Dynamic linking can be tricky to get right and varies by platform, so testing is a must.

--

Related:
#39
#39 (comment)

[Ivorforce]

It is possible to run Godot in CI. I do it myself for a project using abarichello/godot-ci. Based on that image, unit tests could be implemented that run all of these tests on a live godot-python environment.