Hi, I'm not really a Windows stakeholder, but want to give my voice for Conan as it looks very reasonable. The PR I raised on github was the result of quick-play with Conan to see how it fits and how easy is to integrate with cmake and I really was impressed by it.
The pros of Conan are: - easy installation, one click in Windows. Can be installed with pip - CMake integration - just add a conanfile.txt with the description of packages that are required and include conan generated cmake file and it's done (in theory). Some packages are provided with FindXXX.cmake file that take into account some conan-specific info during library search (like name of the library that may be non-standard due to storing libraries for multiple configurations: MT, MTd, MD, static, dynamic, etc - cmake can automatically run 'conan install' - conanfile.txt can be versioned and is easy to read - support for multiple compiles, so (in theory) can be used with VS, clang, gcc (didn't tested that yet, will try to test that this week) - multi-configuration support: release vs debug, different runtime version, different architectures There are of course some cons of that package manager like: - not package signing yet (https://github.com/conan-io/conan/issues/773) - some libraries are not present in the repository and should be packaged first - not all packaged provides custom FindXXX.cmake files and due to that cmake have sometimes problem with finding conan-provided libraries Cheers Robert 2016-12-31 5:28 GMT+00:00 Larry Gritz <[email protected]>: > Brainstorm time... > > It continues to be difficult, especially for newbies, to build OIIO from > scratch on Windows. Building the dependencies are a big part of the hassle. > This is exacerbated by my lack of experience with and access to a Windows > machine (though I did manage to eke out an Appveyor build script, which > despite being very clunky has drastically cut down the frequency with which > I break the build on Windows). > > Robert has proposed enhancements that allow a build of many critical > dependencies using Conan (https://conan.io/) here in this PR: > https://github.com/OpenImageIO/oiio/pull/1593 > > I want to put that PR on hold slightly to allow for wider discussion here > of the alternatives, so that we can collectively decide the best way to > achieve this. (And by "we", I mean consensus of the stakeholders who depend > on Windows builds and know more than I do about how to achieve it. > > I think the two goals, which may or may not have identical solutions, are: > (a) for people who need to use OIIO source code (for example, > developers/contributors) to have an easy way to get/install OIIO's > build-time dependencies; and (b) for people who only need OIIO binaries and > libraries to be able to install both the dependencies and OIIO itself as > easily as possible (ideally just binaries, or if from source, then as close > as possible to a foolproof one-command download, build, and install of > everything). > > Possible systems/strategies include: > https://conan.io/ Conan package manager > https://github.com/Microsoft/vcpkg Microsoft Vcpkg > https://github.com/meshula/mkvfx Nick Porcino's "mkvfx" project > > Are there others to also consider? > > Maybe take a look at all of these and see what you guys think about the > relative merits of supporting/using one or more of them as our strategy for > easier OIIO builds and dependency installation? > > > -- > Larry Gritz > [email protected] > > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > -- My public key can be found at https://keyserver2.pgp.com
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
