On Aug 27, 2012, at 9:36 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
> 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. Do it in python. But you don't need to screw with the -I since the compiler always looks inside the frameworks for the include based on #import <OpenGL/gl.h> etc. That's right the -framework flag is actually ignored at compile time and only needed to link the program so Apple is bogus big time man. and why bother with -L etc etc. Just list the damn library by its full path and pass that to cmake? Barry
