If you don’t have to debug on windows MXE will work..

 

However I highly recommend using CMake rather than QMake, it just works better… 
 (not baiting a flame war, my opinion only)

 

Building Qt for your compiler (dev studio) is easy, but takes a couple hours 
depending on your machine.. But it’s a one time hit.

 

Then you will have the choice of QtCreator on windows or Dev Studio


Scott

 

 

 

From: interest-bounces+scott=onshorecs....@qt-project.org 
[mailto:interest-bounces+scott=onshorecs....@qt-project.org] On Behalf Of Diego 
Iastrubni
Sent: Tuesday, June 19, 2012 5:14 AM
To: Chasc
Cc: interest@qt-project.org; Nikos Chantziaras
Subject: Re: [Interest] Porting Qt app to windows

 

On Tue, Jun 19, 2012 at 6:08 AM, Chasc <ch...@tpg.com.au> wrote:

OK, I have MXE working like a charm. Thanks! The problem though is that
it builds everything statically. I am not sure how this sits with
Nokia's LGPL licence agreement although my software is not for sale and
is only being used in-house. How would I get on publishing a GPL app?
(Pardon my ignorance here)

 

ןֳאקרמשך ודשעק?On Sun, 2012-06-03 at 00:47 +0300, Nikos Chantziaras wrote:

> On 01/06/12 14:49, Chasc wrote:
> > I have recently developed a C++ desktop application in Linux using Qt
> > Creator and have successfully opened the project in the Windows version
> > of Qt Creator. The app runs successfully in the windows Qt Creator IDE
> > but fails to run independently on the Windows platform. I do not have
> > the same problem in Linux.
> >
> > So how can I package this app to run on other Windows machines using
> > dynamic linking? I have tried including QtGui4.dll, QtCore4.dll,
> > libgcc_s_dw2-1.dll and mingwm10.dll libraries in the release directory
> > but all I get is something about a procedure entry point not being
> > located in QtCore4.dll. I am using Qt 4.7.4.
>
> If you're not using WebKit*, I recommend MXE (http://mxe.cc <http://mxe.cc/> 
> ) for
> building Windows executables directly from Linux.  Hasn't let me down yet.
>
> * WebKit is broken for static linking.

 

Internal usage? Not distributing? No problem. you are not obligated to share 
your application, and not the modifications you did to Qt4. LGPL applies only 
to distributing your application.

_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to