Installation and Deployment

@amigo421 hi i know 100% between mingw and VS is a no go, but also seen that sometimes versions of VS also is no good.

i still think there is simpler explanation for your issue. The linker can't even find the lib file specified. Are you really sure that the libs are in "C:\source\icu2\lib"? And not in a release/debug subfolder, etc.?

@jsulm i did not do anything on the android device

Hi, The basics can be found here Don't forget the licensing implication of a static build.

@Bart_Vandewoestyne said: we're storing our Qt build in our version management system This is a strange thing to do, since Qt guarantees binary compatibility between minor versions, but well, you're free to choose. Unfortunately, I don't see how you could decrease the size further, beside deleting the docs, as the libraries are in the /lib directory and they're the next biggest size. Maybe store only the libs that you're using, i.e. these that you're going to deploy. No point in keeping QtXml if you're not using it, right?

Have now refined Avast to just stop checking executables and all still OK. I have not seen any mention of the possible clash with anti-virus software in any of the places I hunted for solutions. I think it should go in a FAQ somewhere. It would have saved me hours of frustration. Such a simple solution that I would never have thought of.

@Krag Hi Maybe just uninstall and install to c:\qt if possible Im not 100 sure its the issues but looking at the screenshot, it seems like. If you move it by hand, im not sure all paths match up. But you can try and see if it still works :)

Hi, I tried to locate the files in my app folder - not working.

Can you post the content of the Makefile.Debug file?

it's happen sometimes. I am investigating on it. I think it is a side affect from android simulator which was running in Automation Test. It could be performance issue.

yes I did. I think I will switch to another tool and give it a go there, TDM GCC is not the best set up for cross compiling I guess.

There's also QIF, the Qt Installer Framework that you should take a look at. It has several interesting features like the update handling.

Thanks for your response. I'm trying this...

@jsulm said: @Pixtar You can use Visual Studio 2013 Community which is more or less same as Professional. Thanks for the hint. :D

That's a good news but still a strange mystery… By the way, no need to modify the thread title, you can mark it as solved using the "Topic Tool" button :)

Indeed, going with bundled xcb helps. I was able to successfully build whole 5.5.1 My app works OK with EGLFS. This time EGL on X11 is disabled by configure automatically however. Thx for help!

I did delete the build directory after it installed, so I'll do it again, and see if it works that time. I wrote a small batch file so I wouldn't have to keep retyping things: @set /p sourcedir= "Enter the source directory " @set /p mingwpath= "Enter the mingw installation path " @set /p builddir= "Enter the build directory " @set /p finaldir= "Enter the final directory " cd %builddir% call %sourcedir%\configure -prefix %finaldir% -debug-and-release -opensource -confirm-license -nomake examples -no-icu -skip webengine -opengl desktop @echo configuration finished pause call mingw32-make @echo making finished pause call mingw32-make install @echo installing finished pause I removed the bit which added to the path after I'd done that once so that I didn't end up with duplicates in my path. EDIT: Okay, it's finished making again, and it's produced exactly the same thing in the install directory (unsurprisingly). There is a qmake.exe in the build directory however, in fact the contents of the two are completely different. The install directory has the following folders: bin (4 exes and 24 dlls, nothing that has qmake in the name) include (one folder per module) lib (two folders and a load of prl files and a files) mkspec (a modules folder which contains lots of pri files) plugins (three folders, each full of dlls) The build folder has qtbase, which contains the above as well as a few other folders including a qmake folder. It also has a qmake exe in the bin folder.

I had a similiar problem when compiling qt5.5.1 for imx6 Platform with eglfs plugin support on Linux (Mint debian) I used following configure options: ./configure -v -opensource -confirm-license -no-xcb -opengl es2 -make libs -eglfs -qpa eglfs -device linux-imx6-g++ -xplatform linux-arm-gnueabi-g++ -device-option CROSS_COMPILE=/opt/imx6_toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2013.10_linux/bin/arm-linux-gnueabihf- -sysroot <imx6_rfs> -prefix /opt/qt5.5.1 After successfull generation of "configure" and trying to compile qt I get following error: <path_to_EGL_headers>/EGL/eglvivante.h:244:2: error: #error "Platform not recognized" #error "Platform not recognized" I've searched for the origin of the problem and found a little error (perhaps even a bug) in the file: qt-everywhere-opensource-src-5.5.1/qtbase/src/plugins/platforms/eglfs/Makefile.eglfs-plugin The CFLAGS and CXXFLAGS missed a Option which is spezified in the device "linux-imx6-g++" qmake.conf file (IMX6_CFLAGS = -march=armv7-a -mfpu=neon -DLINUX=1 -DEGL_API_FB=1) LINUX and EGL_API_FP are important macros to specify the needed EGL Platform API. In case both are not set, compiler will choose the "#error "Platform not recognized" macro. So I've added this to options (-DLINUX and -DEGL_API_FB) to my Makefile.eglfs-plugin: . . . CFLAGS = -pipe --sysroot=/mnt_rfs -O2 -fvisibility=hidden -fno-exceptions -Wall -W -D_REENTRANT -fPIC $(DEFINES) -DLINUX -DEGL_API_FB CXXFLAGS = -pipe --sysroot=/mnt_rfs -O2 -fvisibility=hidden -fvisibility-inlines-hidden -std=c++0x -fno-exceptions -Wall -W -D_REENTRANT -fPIC $(DEFINES) -DLINUX -DEGL_API_FB . . . After that the correct API was chosen from the compiler.......... The strange thing I don't understand is, in the file Makefile.eglfs_device_lib both options are correctly set ?! So perhaps it's a bug/error in the qmake configuration file, but I don't know exactly. This Post maybe not exactly that what are you looking for....but perhaps somebody other will find it useful.