mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] Request for summarized instructions.


From: Tony Theodore
Subject: Re: [Mingw-cross-env-list] Request for summarized instructions.
Date: Tue, 19 Nov 2013 13:36:01 +1100

On 15 Nov 2013, at 8:11 am, Jos De Laender <address@hidden> wrote:

> Dear,
> 
> I used some time ago MXE for a Qt4 based program.
> This worked pretty well.
> The build is however a static link, giving some licensing challenges.
> 
> Following the list and dispersed info on the web it *seems* like you 
> meanwhile can also build dynamically linked (and for w64 ?).
> 
> As a non-specialist (I 'just' want to get my program compiled for Windows) 
> I'm not seeing clear anymore how to use mxe.
> 
> Can someone explain on a fairly basic level how I would build a Qt4 
> application, dynamically linked, preferably 64 bit ? Or is such description 
> somewhere available ?
> 
> Many thanks.

Hi Jos,

The shared builds of Qt4 are still in an experimental branch, but if you want 
to help testing, that would be great. We’ve decided on the target naming[1] so 
there will be no other user-facing changes, just internal changes.

To get started:

export MXE_DIR=~/mxe-shared
git clone -b shared-using-target https://github.com/tonytheodore/mxe.git 
$MXE_DIR
# optionally create a symlink to a previous pkg directory
# disable qt demos
sed -i 's,-make demos,-nomake demos,' $MXE_DIR/src/qt.mk
make -C $MXE_DIR qt MXE_TARGETS=x86_64-w64-mingw32.shared
export PATH=$MXE_DIR/usr/bin:$PATH

After that, you should be able to follow the steps in the tutorial:

http://mxe.cc/#tutorial-5a

to build your project depending on which build system you use. If you had some 
previous build scripts, replacing "i686-pc-mingw32” with 
"x86_64-w64-mingw32.shared” and adding config options for shared builds should 
be all that’s required.

Hope that helps.

Tony


[1] 
http://lists.nongnu.org/archive/html/mingw-cross-env-list/2013-11/msg00020.html


reply via email to

[Prev in Thread] Current Thread [Next in Thread]