This basically means "integrate Empyrean into the payload generation process by modifying it and inventing an EmpyreanResult object", then "get everything to run on Windows through a command".
Most likely, that just means including a hardcoded configuration in the buildchain and using Emyprean's built-in build system. Since Windows docker images don't really exist, we might just take the approach of doing the following:
In a fork of Empyrean, reconfigure it so that it spits out everything in a format we can generally understand
Build the PyInstaller executable in a VM
Commit the executable to the forked Empyrean repo
Include the executable as part of Pygin's repo itself, or download it dynamically on payload generation
Of course, the thing is that we haven't really been building for Windows, which is related to #72. So this will take some work to get correctly.
This basically means "integrate Empyrean into the payload generation process by modifying it and inventing an EmpyreanResult object", then "get everything to run on Windows through a command".
Most likely, that just means including a hardcoded configuration in the buildchain and using Emyprean's built-in build system. Since Windows docker images don't really exist, we might just take the approach of doing the following:
Of course, the thing is that we haven't really been building for Windows, which is related to #72. So this will take some work to get correctly.