-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor and improve Windows builds #162
Conversation
90f283c
to
f507f55
Compare
This requires ocaml/opam#5514. |
"unzip"; | ||
"git"; | ||
"m4"; | ||
"perl"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why does this require Perl? Dropping vim
seems reasonable for CI images though it might surprise some users of the Windows images.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually the perl dependency comes from git. Perl is listed in the installation instructions of OCaml for Windows. We'll drop it once we remove OCaml for Windows.
I'm inclined to remove vim and nano altogether from the CI images, but as it may break workflows we don't know about I won't do it. I thought that starting from scratch, the Windows images didn't need them.
from avsm/ocaml-dockerfile to ocurrent/ocaml-dockerfile.
Light internal refactoring.
Otherwise I always forget why vc-redist is needed.
mingw images also don't need msvs-tools.
I've found out that opam won't bootstrap OCaml without this under MSVC.
It's specific to mingw.
opam was being build with mingw even in the msvc images. Separate mingw and msvc builds into two functions. Separate the msvc build into more build steps. Fix the origin of Install.cmd from avsm/ocaml-dockerfile to ocurrent/ocaml-dockerfile.
See diff at ocurrent/docker-base-images#223.