I have created a modified version of G+Stools that has an additional, optional, parameter of 'quickhex'. If the new G+Stools is called with the quickhex parameter, it will, in turn, call QuickHEX.bat (also included in the .zip file) which bypasses the header file validation that slows compilation while running GCB from within a WINE environment.
This allows the option of adding a command to the Tools > External Tools menu for a 'Quick Hex' compile, whilst retaining the original 'Make Hex' command with the security of full file validation.
The modified G+Stools.exe, G+Stools.bas (source code for the .exe) and the QuickHEX.bat files can be found here:
I have only tested this on my Mac here and at work, but see no reason why this shouldn't work within any WINE host. For the Mac, the files can be copied into place by locating the GCB 'WINE' App, right clicking on it and selecting 'Show Package Contents' > Contents > Resources > drive_c > GCB@Syn > G+Stools and then making a backup copy of the original G+Stools.exe before copying in the new files, G+Stools.exe and QuickHEX.bat. G+Stools.bas is only required if you want to inspect the modified version, or re-compile it under FreeBasic.
Last edit: mkstevo 2016-08-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This needs to be called using the following settings for the external tools. I've added a picture to remind me as much as anyone else of the settings required to correctly call the QuickHEX batch file, and in turn the modified G+STools. After updating SynWrite and or the compiler these settings can become lost and it has just taken me an hour of headscratching to remember how it was done.
I have created a modified version of G+Stools that has an additional, optional, parameter of 'quickhex'. If the new G+Stools is called with the quickhex parameter, it will, in turn, call QuickHEX.bat (also included in the .zip file) which bypasses the header file validation that slows compilation while running GCB from within a WINE environment.
This allows the option of adding a command to the Tools > External Tools menu for a 'Quick Hex' compile, whilst retaining the original 'Make Hex' command with the security of full file validation.
The modified G+Stools.exe, G+Stools.bas (source code for the .exe) and the QuickHEX.bat files can be found here:
Modified G+STools
I have only tested this on my Mac here and at work, but see no reason why this shouldn't work within any WINE host. For the Mac, the files can be copied into place by locating the GCB 'WINE' App, right clicking on it and selecting 'Show Package Contents' > Contents > Resources > drive_c > GCB@Syn > G+Stools and then making a backup copy of the original G+Stools.exe before copying in the new files, G+Stools.exe and QuickHEX.bat. G+Stools.bas is only required if you want to inspect the modified version, or re-compile it under FreeBasic.
Last edit: mkstevo 2016-08-02
This needs to be called using the following settings for the external tools. I've added a picture to remind me as much as anyone else of the settings required to correctly call the QuickHEX batch file, and in turn the modified G+STools. After updating SynWrite and or the compiler these settings can become lost and it has just taken me an hour of headscratching to remember how it was done.