update

[Dirk Hohndel]

On Sat, 2013-10-05 at 10:53 -0700, Thiago Macieira wrote:
> On sábado, 5 de outubro de 2013 00:38:47, Dirk Hohndel wrote:
> > I needed things like
> > 
> > /opt/local/include/QtCore -> /Library/Frameworks/QtCore.framework/Headers
> > /opt/local/include/QtNetwork ->
> > /Library/Frameworks/QtNetwork.framework/Headers
> > 
> > etc.
> > 
> > Thiago, what am I doing wrong?
> 
> My guess is: nothing.
> 
> I guess our buildsystem is simply not prepared for dealing with Qt built with 
> frameworks support. It's possible that it's even a pkg-config limitation that 
> it does not understand -F flags to the compiler.
> 
> I personally have no system-wide installed Qt on my Mac like that (it 
> interferes with my multiple builds). It's also a deprecated method: for Qt 5, 
> we switched to doing it like Apple and not install it system-wide.
> 
> Anyway, what does pkg-config --cflags QtCore return for you on that system, if 
> anything at all?
> 
> It should have an -FQtCore flag.

Qt packages from the qt-project.org don't even install pkg-config
files :-(

I had to manually create them. I'm quite frustrated with the way Qt is
packaged, TBH. One of the reasons we walked away from Gtk and to Qt was
the promise of decent support for Windows and Mac.
Have you looked at the instructions to build a Mac bundle???

Read through this
http://qt-project.org/doc/qt-5.0/qtdoc/deployment-mac.html and tell me
with a straight face that the Qt people who thought that is a user
friendly solution were not completely stoned when they wrote that.
It's batshit crazy. Even Gtk has better tooling than that. As a matter
of fact, I'm considering hacking the Gtk tools to build my Qt bundle.

That's an embarrassment. 

/D