Hahaha, yes that’s always a reasonable option! To save my reputation I will say: it wasn’t my machine…
We did manage to get it running with Cygwin. For those who are interested I’ll post how we did it.
Download Cygwin from here: https://www.cygwin.com/
Then install the package, there will come a point where it asks you to select extra packages to install. In the top of this section there is a search bar. Go into the search bar and search for the following terms:
vim: Install the main one titled ‘vim’, we also installed a bunch of others to be sure, not knowing what might work. If you don’t know what it is it’s just a text editing tool which comes in handy when using the terminal.
gcc: I guess it depends on your chipset, but we installed all the x86 packages that were labelled as developer (or ‘devel’), along with others which weren’t labelled with any particular chipset to be on the safe side, so that’s ‘gcc-fortran’, and some others, also all labelled ‘devel’.
make: Install make and cmake, just searching make will bring up both of these, go for the packages which are labelled simply ‘make’, and ‘cmake’, we didn’t install any others.
others?: There may have been some others but I don’t have the list to hand right now, if you know of any other requirements post them below.
Once you’ve downloaded all the packages above you can run the compilation command within Cygwin just as you would within a Unix terminal: cd Src followed by ./mkgulp . If you run into any problems during compilation it will generally give you a prompt which will let you know what extra packages you need to include in you Cygwin installation. Rerun the Cygwin setup, and select the new packages and try again!
One final note, there is an Include header in the standard gulp make file which points to a folder which doesn’t exist on the windows operating system, it’s something like usr/local/include. That means on compilation you’ll get a warning on every compile that usr/local/include is a bad include and doesn’t exist. Don’t worry about it, it makes no difference to the compilation, and we compiled and ran gulp just fine!
You should now have a working gulp binary! Try running some of the examples in the examples folder within Cygwin!
Thanks again Julian for the great information! Fortunately I didn’t have to mess around with makefiles this time!! Out of interest I see GULP is now 6.0 and it seemed to compile fine with gcc-10.2.*, was that the purpose of the update? Or are there more new features?