Best would be to have OpenImageIO produce and install a CMake config package instead. They are the preferred solution these days, specially for projects using CMake.
If a find module has to be contributed somewhere, it should be to upstream CMake. However, it is likely they will reject it and advise to write a CMake config package instead. They are not that hard to write. Ghis On Sun, 2017-01-15 at 16:15 -0800, Solomon Boulos wrote: > +bigler > > Why not contribute it upstream to CMake? Other projects people build would > certainly benefit from that more than having to make install it. > > James contributed FindCUDA IIRC, and could presumably provide pointers on the > process. > > On Jan 15, 2017 8:33 PM, "Larry Gritz" <[email protected]> wrote: > > I have written a nice FindOpenImageIO.cmake file that's great for projects > > to find the headers & libraries of OIIO. I want to distribute that as part > > of OIIO. What's the right place to put it in the distribution or install > > area? > > > > > > -- > > Larry Gritz > > [email protected] > > > > > > _______________________________________________ > > 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 _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
