On Mon, Aug 27, 2012 at 9:15 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> All you need do is search through the framework directories (Sean kindly > provided the list) for xxxx.framework then the dynamic library is in that > directory called xxxx (yup no suffix!). Now you have a complete path to > pass to cmake. I am kind of surprised that someone hasn't provided a cmake > utility to do this already (since it must be very common), perhaps > > Google finds some odds and ends like this > http://twogregui.googlecode.com/svn/trunk/TwOgre/cmake/OgreFindFrameworks.cmake > but like everything associated with cmake it is incomprehensible. Side > question: why do all configure systems have to be so fucking > incomprehensible? > I know, it's such a disaster. I don't know whether it's better to write that damn custom CMake logic in CMake or to just do it in Python, converting to -I/-L/-l/-Wl,-rpath options. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120827/6d78d4dd/attachment.html>
