On Mon, Apr 16, 2012 at 3:13 PM, Larry Gritz <[email protected]> wrote: > For the problem of your having a weird custom Qt (or other library) used by > a 3rd party App that would prevent you from having a standard Qt in the > normal place... well, maybe we can alter our CMake files to allow an > explicit override for where OIIO looks for Qt
I think this is already catered for by the standard FindQt.cmake - just set QT_QMAKE_EXECUTABLE to point to the path of your alternative qmake. > (or even overrides for every major dependency). The standard Find*.cmake files usually honour CMAKE_PREFIX_PATH (and more specifically CMAKE_INCLUDE_PATH / CMAKE_LIBRARY_PATH for includes and libraries respectively). Some complicated cases like boost and Qt have their own special variables (BOOST_ROOT, and QT_QMAKE_EXECUTABLE as above). All up, as long as we haven't done anything too "special" in our build system I think overrides should generally be possible already. ~Chris _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
