Until now, the start_myofinder.bat script has been distributed by the myofinder.msi installer, and used for starting MyoFInDer. To avoid the startup script to be modified by users, and to distribute an actual startup executable rather than a text file, this PR replaces the start_myofinder.bat script with a myofinder.exe executable.
The executable is built with gcc, from the myofinder.cpp source file (added in 0d5f80ab). It performs roughly the same actions as start_myofinder.bat did, with some minor adjustments. The configuration file for the Advanced Installer application (config.aip) was modified accordingly (51a66135), as well as the build_windows_installer.yml file managing an automated GitHub workflow (5249656e). start_myofinder.bat was removed from the repository (79fee1ce). The documentation was updated so that users don't get confused between myofinder.msi and myofinder.exe, both located in the bin/ folder (fcd55e57 and 1483d876).
Until now, the
start_myofinder.batscript has been distributed by themyofinder.msiinstaller, and used for starting MyoFInDer. To avoid the startup script to be modified by users, and to distribute an actual startup executable rather than a text file, this PR replaces thestart_myofinder.batscript with amyofinder.exeexecutable.The executable is built with
gcc, from themyofinder.cppsource file (added in 0d5f80ab). It performs roughly the same actions asstart_myofinder.batdid, with some minor adjustments. The configuration file for the Advanced Installer application (config.aip) was modified accordingly (51a66135), as well as thebuild_windows_installer.ymlfile managing an automated GitHub workflow (5249656e).start_myofinder.batwas removed from the repository (79fee1ce). The documentation was updated so that users don't get confused betweenmyofinder.msiandmyofinder.exe, both located in thebin/folder (fcd55e57 and 1483d876).