#291: Improve the MinGW build on TeamCity --------------------------+------------------------------------ Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: minor | Milestone: Component: Olena | Version: 2.0 Resolution: | Keywords: continuous integration --------------------------+------------------------------------ Old description: New description: The current MinGW build running on the !TeamCity server (http://teamcity.lrde.epita.fr/viewType.html?buildTypeId=Olena_I686w64mingwG…) is limited to the compilation of a subset of Olena: many features are disabled as we cannot run programs built by `i686-w64-mingw32-c++` or even link them with most of our external dependencies (such as !GraphicsMagick). Likewise, the rebuilding of the documentation is circumvented by `touch`-ing timestamps and output files generated by locally-built Milena programs. Could we use Wine (http://www.winehq.org/) to run binaries built by `i686-w64-mingw32-c++`? Or run them on a Windows host (either an actual machine or a VM)? Here is a summary of things that could be improved: * Do not run programs in `milena/doc/` — or have them run in the host environment (Windows). This is currently circumvented by not passing `--enable-apps` to `configure`. * Do not use the `random()` function (used at least in `milena/apps/mesh- segm-skel/`) as MinGW does not provide it. * Enable support for !GraphicsMagick (or !ImageMagick) and Qt. * Enable the `make check` and `make distcheck` !TeamCity build steps. * More generally, be able to pass `--enable-all` to `configure`. -- Comment (by levill_r): Update URL. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/291#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform