Re: [Mingw-cross-env-list] Configure options for qt

[Mark Brand]

> For instance, in one of my projects I need to link against some
> image libraries explicitly when doing the static win32 build.
> This is easily done in my *.pro file via:
>
>     ...
>     win32 {
>         LIBS += -liconv -ljasper -ljpeg -ltiff -lmng -lIlmImf ...
>     }
>   

(This is worth repeating I think.)

For static plugins, the plugin library can still end up with unresolved
symbols because qmake puts it in the makefile after the libraries
specified in LIBS.  I described a workaround in an earlier post:

> A remaining issue arises when your static Qt plugin depends on a static
> library outside Qt. This obviously comes up in mingw-cross-env. For
> example, qsqlpsql might depend on pq. In such cases "QTPLUGIN +=
> qsqlpsql" is not enough to get qmake to create a Makefile that links to
> pq.  What seems to work is "QTPLUGIN += qsqlpsql pq", but I don't know
> if this is the best way to solve the problem.
>   

As Phep mentioned, a realistic example is:

> QTPLUGIN += qsqlpsql pq secur32 ssl crypto crypt32
>