Hi all - I think it would be enough if OIIO honors the CMAKE_PREFIX_PATH variable when trying to find all dependencies, including IlmBase and OpenEXR. By doing that developers with the original external package or their own could easly use it to find all dependencies (no system installs needed). @Stephan and Nicholas: Did you have a look at BundleUtilities ( http://www.cmake.org/Wiki/BundleUtilitiesExample)? Will do some tests with it tonight. Mikael
On Mon, Feb 13, 2012 at 9:04 AM, Nicholas Yue <[email protected]>wrote: > ** > On 13/02/12 6:58 PM, Stefan Werner wrote: > > On 08.02.2012, at 19:30, Larry Gritz wrote: > > > So, I put it to all of you: > > * Does anybody still have the need to separately compile the dependencies > rather than use your system libs (and package manager)? > > My OS X build is using the externals directory instead of package manager > libraries so that I can distribute copies to users who have nothing but a > stock OS. I'm linking against static libraries where possible/permitted, and > am providing side-by-side dylibs for the rest. > > I am doing the same for my Windows x64 build for distribution. > > * Is there any point to keeping the external project going at all, or at > this point should we just delete it and replace with the list of what > packages are needed and where to get them from? > > As long as the build process respects THIRD_PARTY_TOOLS_HOME, I'll be fine. > > +1 > > Best regards > -- > Nicholas Yue > Graphics - RenderMan, Visualization, OpenGL, HDF5 > Custom Dev - C++ porting, OSX, Linux, Windows > http://au.linkedin.com/in/nicholasyue > > > _______________________________________________ > Oiio-dev mailing list > [email protected] > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org > >
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
