Is there no open source package manager we can recommend for Windows to make it easy to install all the dependencies in standard places in one shot?
OS X doesn't have a package manager built in like the Linux distros do, but there are still packages such as Macports and Homebrew that make this easy for all the common open source tools. Is there any equivalent for Windows? On Mar 21, 2012, at 5:44 PM, Steven Caron wrote: > i have tried to build oiio from Release-1.0.2 and i am finding the cmake > setup doesn't take into account 'THIRD_PARTY_TOOLS_HOME' very well. despite > setting this cmake fails to find zlib, png, tiff, and jpeg. the INSTALL file > does mention this but i feel this should be taken care of in the cmake > process. > > i am also noticing the externals that are downloaded arent organized the way > that externalpackages.cmake is expecting them to be. it expects... > > \external > \dist > \windows > \include > \glew-1.5.1 > \ilmbase-1.0.1 > \jpeg-6b > \libpng-1.2.3 > \openexr-1.6.1 > \tbb-21_20080605oss > \zlib-1.2.3 > \tiff-3.8.2 > \lib > \glew-1.5.1 > \ilmbase-1.0.1 > \jpeg-6b > \libpng-1.2.3 > \openexr-1.6.1 > \tbb-21_20080605oss > \zlib-1.2.3 > \tiff-3.8.2 > > the new externals package is organized like so... > > \external > \dist > \windows > \glew-1.5.1 > \ilmbase-1.0.1 > \jpeg-6b > \libpng-1.2.3 > \openexr-1.6.1 > \tbb-21_20080605oss > \zlib-1.2.3 > \tiff-3.8.2 > > > so to improve building when using 'THIRD_PARTY_TOOLS_HOME' i attempted to go > to the individual plugin folders and modify the CMakeLists.txt to handle when > 'THIRD_PARTY_TOOLS_HOME' is set and deduce where their respective library and > include directories and set some variables, then still call find_package() to > make sure CMake actually finds them. the only issue is that when > 'EMBEDPLUGINS' is set, find_package() is called inside libOpenImageIO > CMakeLists.txt and fails still. > > i really hope a GSoC participant can look at these issues and provide some > fixes. > > On 3/21/2012 10:09 AM, Steven Caron wrote: >> thanks for this, going to try building today. then on to attempting oiio too. >> >> s > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
