Fetch binary tools with build script, hide them with .gitignore

The following bloat the repository and will lead to a slow, agonizing death:

• WurstPack\bin\worldedit.exe
• WurstPack\wurstscript\wurscript_b.exe
• WurstPack\vexorianjasshelper\jasshelper.exe
• WurstPack\vexorianjasshelper\clijasshelper.exe
• WurstPack\vexorianjasshelper\pjass.exe
• WurstPack\vexorianjasshelper\pjass_old.exe
• WurstPack\bin\exehack.exe
• WurstPack\mpqedit\mpqeditor.exe
• WurstPack\wurstscript\MpqCL.exe
• WurstPack\wurstscript\wurstscript.exe
• WurstPack\grimext\PatchGenerator.exe
• WurstPack\grimext\FileExporter.exe
• WurstPack\grimext\FileImporter.exe
• WurstPack\grimext\TriggerMerger.exe
• WurstPack\winmpq\WinMPQ.exe
• WurstPack\grimext\ObjectMerger.exe
• WurstPack\grimext\ConstantMerger.exe
• WurstPack\grimext\grimex.dll
• WurstPack\grimext\TileSetter.exe
• WurstPack\grimext\PathMapper.exe
• WurstPack\tesh\funclist.db
• WurstPack\tesh\horus.dll
• WurstPack\tesh\tesh.dll

If they are generated by WurstScript (successful builds) gitignore them. If they are tools required by WurstScript (libraries) fetch them with some equivalent of make config (I suppose you use ant), and gitignore them.

[peq]

Well, it’s kind of happening. But slowly.

• Frotty has started a new version of the standard library in a separate repo: https://github.com/Frotty/StdLib2
• The new editor based on vscode is in a separate repo: https://github.com/peq/wurst4vscode

Once the new editor based on vscode is stable enough, I can ditch the Eclipse plugin (or at least entangle it from the compiler). Without the need for the Eclipse build system it becomes easy to use proper dependency management with gradle.

So check back next year for this issue 😃

[peq]

Seems to work