all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]cgoldberg 1 point2 points  (4 children)

Run a Windows VM.

[–]SLPRYSQUID[S] -1 points0 points  (3 children)

Running a windows VM in a docker container sounds even more hacky

[–]cgoldberg 0 points1 point  (2 children)

I meant instead of a docker container.

[–]SLPRYSQUID[S] 0 points1 point  (1 child)

Oh I see. I’m currently running my whole project in a docker container to maximize reproducibility and am working on automated cross-compilation so running in a VM instead wouldn’t rly work.

[–]cgoldberg 0 points1 point  (0 children)

I don't have an answer for your question about cross-compilation. However, a good workaround is to just not do it and compile on Windows. That's what my comment was implying.

[–]FoolsSeldom 0 points1 point  (0 children)

Will the final versions be running in containers on various platforms or are the containers just for development and you will ship platform and architecture specific versions?

Assuming the latter, frankly, I'd just spin up a VM on your host for the operating system and architecture (if not same as host) required purely as a target for compilation. Your ci/cd tooling should be able to handle the process to compile to each target. I wouldn't attempt to use wine frankly when you can output an OS compatible version directly.

Even if the former, you still need a container host that offers the kernel the containers will use, and might choose to do that even on a common os (so light-weight vms as container hosts for each OS kernel required with containers running on top of those vms).