<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On 29 May 2015, at 16:10, Thomas Braibant <<a href="mailto:thomas.braibant@gmail.com" class="">thomas.braibant@gmail.com</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class="">- Finalize OPAM support for Windows (this is listed on the OPAM 1.3 roadmap). When this support is in place, many OCaml packages should work out of the box (with the proviso that many packages assume a unix-ish environment for their build system). <br class=""></div></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br class=""></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">- Discuss how to help package developers improve Windows support. One way to do that could be to provide know-how about how to setup continuous integration on services like Appveyor to check that packages build on typical Windows setups. </div></div></blockquote><br class=""></div><div>One thing I would *really* like to do is to hook in the current experimental bulk builds of OPAM into Windows as well. Right now we use Docker for Linux builds, but the plan is to expand this further (see <a href="https://opam.ocaml.org/builds/" class="">https://opam.ocaml.org/builds/</a> for the logs).</div><div><br class=""></div><div>One way to make the results more useful is to open a brand new opam-repository just for Windows, with the build rules and patches ported over from the old WODI. This could be the 'native' Windows repository, with the Unix one containing the minimal patches required for Cygwin support. Unification could then happen over time, particularly as more declarative systems such as Assemblage mature.</div><div><br class=""></div><div>We don't have the expertise to do the Windows porting here in Cambridge, but are very happy to set up and operate the build infrastructure on virtual machines if someone can point us at an OPAM remote...</div><div><br class=""></div><div>-anil</div></body></html>