Re: [Mingw-cross-env-list] Qt5 question

[Tony Theodore]

On 26 Feb 2014, at 16:48, G Coco <address@hidden> wrote:

> Hi,
> 
> I've been using Qt4 with MXE for quite a while with great results.
> 
> I am trying to build using Qt5 and having some issues and was hoping for some 
> assistance.
> 
> I run qmake and get the following info in the Makefile.
> 
> MAKEFILE      = Makefile
> 
> ####### Compiler, tools and options
> 
> CC            = i686-pc-mingw32.static-gcc
> CXX           = i686-pc-mingw32.static-g++
> DEFINES       = -DUNICODE -DGC_WANT_ROBOT -DQXT_STATIC -DGC_HAVE_SOAP
> CFLAGS        = -pipe -fno-keep-inline-dllexport -O2 $(DEFINES)
> CXXFLAGS      = -pipe -fno-keep-inline-dllexport -O2 $(DEFINES)
> INCPATH       = -I. -I'../qwt/src' -I'../qxt/src' -I'../qtsolutions/soap' 
> -I'../../usr/i686-pc-mingw32.static/qt5/mkspecs/win32-g++'
> LINKER      =        i686-pc-mingw32.static-g++
> LFLAGS        =        -mwindows -Wl,-s -Wl,-subsystem,console
> LIBS        =        ../qwt/lib/libqwt.a -lm -lz gc.icns
> QMAKE         = /Users/gc/mxe/usr/i686-pc-mingw32.static/qt5/bin/qmake
> 
> What is happening is that I am not seeing any of the Qt5 include paths and so 
> the compiler can not find any of the Qt includes.
> 
> i686-pc-mingw32.static-g++ -c -pipe -fno-keep-inline-dllexport -O2 -DUNICODE 
> -DGC_WANT_ROBOT -DQXT_STATIC -DGC_HAVE_SOAP -I. -I'../qwt/src' -I'../qxt/src' 
> -I'../qtsolutions/soap' 
> -I'../../usr/i686-pc-mingw32.static/qt5/mkspecs/win32-g++' -o QTFullScreen.o 
> QTFullScreen.cpp
> In file included from QTFullScreen.h:23:0,
>                  from QTFullScreen.cpp:19:
> GC.h:30:19: fatal error: QString: No such file or directory
>  #include <QString>
> 
> Any idea why the INCPATH does not have the Qt5 include paths listed?
> 
> I have this code building on a Mac and Linux natively and see all the include 
> paths in the Makefile.
> 
> Any help appreciated

I’m not a Qt expert, but the only thing I can think of is do you have:

QT += widgets

in your *.pro file? I’m guessing the native builds are installed to system 
locations so you wouldn’t see this issue.

Cheers,

Tony