Closed kevinanewman closed 5 years ago
Ok, looks like I was multi-tasking and took a wrong turn!
The issue was that the sample instructions:
$ ./run
Doesn't work on Windows...
The file would need to be run.bat, so I made one for myself, which is probably how I got turned around!
The goal was to avoid duplicating the contents of run
and runpro
but I think what actually needs to happen is to have a run.bat
and a runpro.bat
with the same contents as their non-bat counterparts.
As a side note, what's interesting is that when running a .bat file, the direction of the slashes doesn't cause a problem (bin/rungui versus bin\rungui) but if you try to pipe the file contents the command line then the direction does matter, so you can't just pipe the original files.
In any case, thanks for your time!
Created .bat files to run the "run" and "runpro" scripts that are otherwise a little awkward to execute on Windows machines