To: cygwin@cygwin.com
From: Phil Bouchard <philippe@fornux.com>
Subject: Re: Qt Creator & static libqt-mt.a
Date: Tue, 12 Jul 2011 22:53:31 -0400
Lines: 27
Message-ID: <ivj1bb$esl$1@dough.gmane.org>
References: <ivg4ok$9o1$1@dough.gmane.org>	 <1310452987.8576.47.camel@YAAKOV04> <ivhvun$q1t$1@dough.gmane.org> <1310524874.3528.8.camel@YAAKOV04>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
In-Reply-To: <1310524874.3528.8.camel@YAAKOV04>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 7/12/2011 10:41 PM, Yaakov (Cygwin/X) wrote:
>
> You don't need to distribute the Qt DLLs, just have your users get them
> from the distro.

I meant some people would like to distribute an executable to systems 
with no Cygwin or Qt installed.

> False.  While some plugins can be builtin to the libraries, the
> following absolutely require plugin support:
>
> - CJK language support,
> - QML (QtDeclarative),
> - QCA,
> - QtDesigner widgets,
> - Phonon,
> - third-party QStyle engines,
> - and last, but not least, KDE.

What I am trying to say is to include both the DLL and the static 
library in the package, this way we'll be able to use Qt Designer and 
linking the final executable dynamically or statically.

As it is right now I've been rebuilding Qt from source 2 or 3 times 
because the configure script deletes all objects files when it's run and 
each build took 96 minutes.  Not to mention I had the following bugs:
http://bugreports.qt.nokia.com/browse/QTBUG-20342?focusedCommentId=158621#comment-158621


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple