Detecting Qt libraries in the 'framework' format

Dentrassi BBQ

An open source project i volunteer with has recently begun work on a Qt client to go alongside the other interfaces. We use the traditional command line configure and make process, and while we are able to build against Qt on linux systems we are so far unable to detect the Qt library on OSX, since those have Qt as a framework. Web searches for "configure detect framework" turn up about a billion hits that have no relevance - can somebody please point me to a FAQ or [better yet] an example project that has successfully dealt with this?

zester

Qt 4.7: Developing Qt Applications for Mac OS X
http://doc.qt.nokia.com/4.7-snapshot/developing-on-mac.html

Qt 4.7: Deploying an Application on Mac OS X
http://doc.qt.nokia.com/stable/deployment-mac.html

goetz

autotools are not very common for pure Qt projects. You might get a quicker answer in some autotools forum.

Of course you could also consider moving to CMake, another more modern configuration tool.

zester

CMake would be a better option than autotools.

Dentrassi BBQ

Next question, and i guess i'll leave it in this thread:

Does libQtGUI exist in the framework? I can't find it with 'locate' and i don't see it when i manually inspect QtGui.framework.

goetz

The path is

QtGui.framework/QtGui.framework

which is a symlink to

QtGui.framework/Versions/4/QtGui

It's not forbidden to 'cd' into the directories and look yourself ;-P

Dentrassi BBQ

As i said, i had manually inspected the framework. I was expecting to find something that started with 'lib' and so ignored QtGui.

Anyway, thanks.

goetz

Ok, thought you had not seen that files.

Seems to be another incarnation of Apple's former claim "Think different" :-)

Oh, and be aware - this naming schemes holds for framework libraries (those within a xxx.framework bundle) only. "Regular" libraries are named the usual libFooBar.dylib, including Qt plugins.

Dentrassi BBQ

Okeh, thanks!