If I recall correctly, CONFIG += static is sufficient with qmake, but
again you need statically-built versions of all of the libraries you
need, including Qt.

/s/ Adam

On Thu, Sep 16, 2010 at 12:40 PM, Daniel Molkentin
<[email protected]> wrote:
>
>  On 9/16/2010 3:49 PM, ext Paul Smith wrote:
>>>> With KDevelop, there is an option "All static libraries" to do that
>>>> automatically;
>>> It changes the project files to add linker instructions to use static
>>> instead of dynamic libraries?
>> I guess so.
>>
>>>> I cannot find a similar option in QtCreator.
>>> You need a static build of Qt to start with, then in the .pro use e.g.
>>> the LIBS variable to directly include the .a files.
>> Is that true even when I use a 'Qt4 console application' project?
>>
> Yes, as soon as you use any Qt functionality, including QCoreApplication
> and friends. KDevelop might offer help there, but it still requires a
> statically linked Qt.
>
> Daniel
>
> --
> Daniel Molkentin, Software Engineer,
> Nokia, Qt Development Frameworks
> website: http://qt.nokia.com
> Rudower Chaussee 13, DE-12489 Berlin
>
> Nokia gate5 GmbH
> Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany
> Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B
> Umsatzsteueridentifikationsnummer: DE 812 845 193
> Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori
>
> _______________________________________________
> Qt-creator mailing list
> [email protected]
> http://lists.trolltech.com/mailman/listinfo/qt-creator
>

_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator

Reply via email to