Thiago Macieira wrote:
Sorry for the delay; I missed this message before leaving on a bit of a
vacation.
...
> When searching for plugins, Qt 4 looked for this build key and compared. If it
> was different, it would refuse to load the plugin.
>
> This functionality was removed in Qt 5. We stil
On Wednesday 22 July 2015 18:51:58 René J. V. Bertin wrote:
> > 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.
The build key is a string that is assign
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 di
On Wednesday 22 July 2015 10:23:20 René J.V. Bertin wrote:
> Hi,
>
> I've spent some time the other day configuring an Ubuntu PPA I've been using
> to build my "system" Qt 4.8.7 to use clang 3.5.1 instead of gcc-4.9. It was
> rather straightforward to get things to build (I had to modify 1 Kubuntu
Hi,
I've spent some time the other day configuring an Ubuntu PPA I've been using to
build my "system" Qt 4.8.7 to use clang 3.5.1 instead of gcc-4.9. It was rather
straightforward to get things to build (I had to modify 1 Kubuntu patch).
The experiment wasn't very conclusive though: my KDE envir
