Closed davidbuzz closed 4 years ago
Thanks, David. Please tell us why exactly did you decide to add another build recipe alongside already existing one?
Existing cx_freeze solution did not work for us, at all.
Okay, I see that, but could you please specify what exactly did go wrong? Any issues, error messages, whatever? We need to know exactly why we are replacing one build recipe with another. Thanks!
Closing due to unresponsiveness.
I reconmend u simply use a clean windows box to try to buid a .exe for yourself and when u are fully informed about how it fails utterly and completely, remember to come back here and reconsider this, which worked for me.
You'll need to edit 'paths' in make_exe3.bat , uavcan_gui_tool.spec.good and UAVCAN GUI Tool2.nsi to match the full-path/s that you are using, but this worked for me.
I now have a windows .exe that works with WPython64-3760 and is built with 'pyinstaller' and the .spec file and then assembled into an 'installer' with NSIS 3.05 from https://nsis.sourceforge.io/Download and the .nsi file