Some ideas are:
- Running the tool inside the built Docker image itself. The issue here is that installing Docker on Windows is not very easy for users. Most of them have to go with the legacy solution Docker Toolbox (either the system requirements don't meet or because its not very comfortable to disable virtualbox, which is a necessity for Docker), which has its own set of problems in our case with high memory usage etc. This again makes it difficult for them to build the tool. However, it could be done for Mac (addressed by EBIvariation/vcf-validator#82), but this needs to be tested. (for users, mac and win)
- Cross compiling the tool on Linux for target Windows using MinGW and Mac using Mac SDK to generate the binaries for users. A dockerfile which does the same could be written so that maintainers can easily provide the binaries directly to users. The problem here is that cross compiling the dependencies of the project (like ODB etc) isn't trivial and quite error prone too. (for users, mac and win)
- Writing a new dockerfile that builds the application for Windows, but again the problem of Docker with Windows persists. This cannot be done for Mac as it is not yet fully supported as a containerized OS. (for developers and users, win)
- Writing a "traditional" script for each Mac and Win. This could be tinkered around if none of the above ways work. (for developers and users, win and mac)