Thiago Macieira wrote:
> It needs to work, because we can't ship all plugins. It does not need to be
> exactly the same way that it was before, but there needs to be a way.
>
> Seeing there's a bug report already, let's discuss ther on how to solve this.
Agreed and agreed.
R.
__
Em terça-feira, 7 de fevereiro de 2017, às 17:25:57 PST, René J.V. Bertin
escreveu:
> This approach is broken in Qt 5.8.0; is it still possible to build these
> plugins separately? Would this work by calling qmake in qtbase/src/sql for
> instance, with the appropriate arguments?
It needs to work,
On Tuesday February 07 2017 17:35:37 Samuel Gaist wrote:
> https://bugreports.qt.io/browse/QTBUG-58372
Indeed, thanks. Removing the QMAKE_USE+=psql line also worked here (plus moving
.qmake.conf into the psql directory).
R.
___
Development mailing lis
> On 7 Feb 2017, at 17:25, René J.V. Bertin wrote:
>
> Hello,
>
> MacPorts has always shipped the Qt sql plugins as separate packages, so the
> main (QtBase) component could be built without unnecessary libraries
> installed. That is, qtbase is configured with -no-sql-$driver
>
> This was im
Hello,
MacPorts has always shipped the Qt sql plugins as separate packages, so the
main (QtBase) component could be built without unnecessary libraries installed.
That is, qtbase is configured with -no-sql-$driver
This was implemented quite simply: to build say the PostGresql plugin we'd
unpac
