First, ask if the module is really necessary. If, instead, you can add an
OpenEXRConfig.cmake file to the OpenEXR project itself, and install it in a
place that cmake's find_package will automatically find it, then a find
module is unnecessary.
However, if that's not possible or practical,
On Thursday 16 June 2011, David Cole wrote:
First, ask if the module is really necessary. If, instead, you can add an
OpenEXRConfig.cmake file to the OpenEXR project itself, and install it in a
place that cmake's find_package will automatically find it, then a find
module is unnecessary.
2011/6/16 Alexander Neundorf a.neundorf-w...@gmx.net:
On Thursday 16 June 2011, David Cole wrote:
First, ask if the module is really necessary. If, instead, you can add an
OpenEXRConfig.cmake file to the OpenEXR project itself, and install it in a
place that cmake's find_package will
On Thursday 16 June 2011, Campbell Barton wrote:
2011/6/16 Alexander Neundorf a.neundorf-w...@gmx.net:
On Thursday 16 June 2011, David Cole wrote:
First, ask if the module is really necessary. If, instead, you can add
an OpenEXRConfig.cmake file to the OpenEXR project itself, and install
Recently I decided to start moving some of our projects hard coded
paths into Find***.cmake modules.
Incidentally the libs are libsamplerate, libFFTW3, libsndfile,
libjemalloc, OpenEXR, OpenJPEG, libpcre.
I started out with OpenEXR, and tried to comply with the module
readme.txt, and used
