[Development] Qt 4.8.7 built with linux-clang-64

[René J. V. Bertin]

Thiago Macieira wrote:

> Anyway, linux-clang isn't supported in Qt 4.8. There's barely any testing done
> with that. In Qt 5, both Olivier and I are maintaining it.

Well, that's enough of a reason for me not to insist, thanks.
Qt 4.8.7 no longer ships the clang mkspecs files in the unsupported directory, 
though.

> What is the build key with Clang? Does it list "gcc-4" or not?

I'm not sure I understand. The clang version I use does use headers from gcc-4 
if that's of any relevance to your question.

> Make sure it even searched those plugins in the first place. Try setting
> QT_PLUGIN_PATH to `kde4-config --path qtplugins`.

It certainly looked like it didn't search those plugins, but that also seems a 
very unlikely reason. I used the exact same Debian/Ubuntu build & packaging 
scripts, edited only to use the linux-clang mkspecs instead of linux-g++ ...
Unless of course the plugin path is set through the mkspecs files.

Is there a way to query the default plugin search path?

...

> Can you check
> if the plugins have a .qtplugin section (objdump -h).
> 
> Actually, just run this on a plugin that won't load:
> objdump -sj.qtplugin /path/to/plugin

Ok, thanks, saving this for future reference. As I said, debugging this would be 
very cumbersome (my Linux rig is severely underpowered for local Qt builds) so 
unless you'd want me to do this I'm going drop clang and set up the PPA to use 
gcc 5.1 instead.

R.