Re: [Mingw-cross-env-list] Question - MXE tutorial Step 4, 5c

[René Berber]

Timothy Gu  wrote:

[snip]
> Yes, it is. PATH is set by bash and some other files too so it is
> completely expected that you can't see another PATH in the file.

Actually, for building with Qt you need additional settings.

What I use for a 64-bit build (32-bit is similar, but different) with
Qt4 is:

export
PATH=/opt/mxe/usr/bin:/opt/mxe/usr/i686-w64-mingw32.static/qt/bin:$PATH

export QTDIR=/opt/mxe/usr/i686-w64-mingw32.static/qt

>> In step 5c Im not quite sure what Im supposed to do:
>> Do I have to open the terminal, then cd to /where MXE is
>> installed/usr/i686-pc-mingw32/qt/bin/ and then enter something like "qmake
>> make" in the terminal?
> 
> No, you are supposed to cd to your *project directory*, then execute the
> steps shown on the website to configure and build your project.

The first export I showed above takes care of adding to PATH the
location of qmake.  So you only change into the top directory of your Qt
project, where there should be a .pro file (which is what qmake uses),
and then follow the instructions.

Again actual use (needs knowledge of Qt) is:

qmake
make -j4 release

or

make debug

depending on your target (debug or release, as per Qt concept).

The -j4 is unrelated, tells make to use parallel make, up to 4
processors (Qt doesn't inherit what MXE uses in its own make).
-- 
René Berber

smime.p7s
Description: S/MIME Cryptographic Signature