#build #Qt5.1.1 with #mingw on #Windows finally suceeded

Three weeks struggling with the compilation of Qt5.1.1, I finally managed to have one built without failure message during compilation.
The main reason for previous failures, in my own opinion, is mainly due to my ignorance of one crusial factor during shadow build.
You should have your source and build folders in the same level, best in same folder.
This information has been mentioned in an old document about Qt shadow build instructions posted in nokia site before but seems cannot find it now. The current documents/wiki on qt-project site do not mention this explicitly but the example has such implied.

[#solved] #Build #Qt5.1.1 #failed again (Makefile.Debug:7091: recipe for target '.obj/debug_shared/qwindowstheme.o' failed)

Find a patch for the file qtbase\src\plugins\platforms\windows\qwindowstheme.cpp.

Need to try again.

#Build #Qt5.1.1 #failed again (Makefile.Debug:7091: recipe for target '.obj/debug_shared/qwindowstheme.o' failed)

Follow the MinGW 64 bit wiki post, I try to build dependent libraries myself before building Qt5.1.1 again.

After applying the patch, I have run into another problem "Makefile.Debug:7091: recipe for target '.obj/debug_shared/qwindowstheme.o' failed".

[#Solved] #Building #Qt5.1.1 static failed (Makefile:350: recipe for target 'qfilesystemengine_win.o' failed)

Finally found a patch on web to solve the issue.

You can download the patch from here.

The file to be patched is <qt-5.1.1-Folder>/qtbase\src/corelib/io/qfilesystemengine_win.cpp

Hope this time the compile can get through.

#GradeOne admission #IQ test

It is a grade one (primary one) admission IQ test. Adult should be able to answer within 30 sec.
I can answer it within 5. How about you?

#GoogleCalendar not #sync with my #Galaxy #S3 #solution

Recently, I've found that there is error in #sync of my #GoogleCalendar with my #Galaxy #S3. Having search on the web without any solution. But I found that installation of #GoogleCalendarApp can solve the issue.

Just successfully compile #QtRpt & #QtRptDesigner with #Qt5.1.1

#QtRpt is a #reportengine for #Qt application. I like its interface as it looks similar to #FastReport. However, it seems to be a startup project which lack of many features that I used with #FastReport, like nested data band, #master-child report, #barcode printing, #export to #Excel, #pdf, #crosstab report, ti name a few.

Though #QtRpt missing many features that I need, it is a good starting point for me to study.

As recently, I'm trying #Qt5.1.1 , I take it as my testing project. The report engine is written using #Qt4 initially(?), and the latest version of #QtRpt is able to be compiled with #Qt5 , it is not the case for its #QtRptDesigner.

Porting of #QtRptDesigner to #Qt5 is much easier than I think. It's just a few replacement/addition of #include clause and add the #Qt version checking in the #project file to add #Qt5 module will be done.

And now, I have a working suite of #QtRpt for testing. :)

#compile #xTuple #OpenRpt with #Qt5 and #QtCreator

xTuple's OpenRpt is a features rich, open source report engine that worth a try.
When compiling with QtCreator with default options, I've got numerous errors saying ui*.h are missing. Check through the project folder, I can found the files but still cannot get through.
Since files in project path, this must be path searching issue that need to be solved.

#g+ #hashtag testing

It seems hash tag in #blog post contents not recognized by #g+ when sharing from #blogger. Even the labels will not be used as g+ hashtag.

What I have tried is to put the hashtag in the title and it seems worked.

Android Blogger app cannot post published blog to g+

Just publish a post on the road with #bloggerApp, and find that it lacks of the web version #automatically post to #g+.

:(

Why there will be two posts in G+ when I publish in blogger?

Anyone know why there will be two #g+ posts being generated whenever I post on #blogger? Though they are not exactly the same, but both link to the same post in my #blog.
Is there any setting control this behaviour?

Remove the yellow ! from the kits of QtCreator's build and run environment for Qt Static build

When configuring QtCreator's Build & Run options with static Qt build, kits item will show a yellow exclamation mark due to x86-windows-unknown-pe-32bit. This seems not affecting the compilation with this static Qt build.
But if you really want to remove that yellow !, you can try to copy the Qt5Core.dll and Qt5Cored.dll from your shared build to the lib folder of your static build.
e.g.

c:\Qt\5.1.1\mingw48_32 (this is installation of the Qt SDK)
c:\Qt\5.1.1\mingw48_32s (the static version)

Then you can 

copy /y "c:\Qt\5.1.1\mingw48_32\lib\Qt5Core.dll" "c:\Qt\5.1.1\mingw48_32s\lib\Qt5Core.dll"
copy /y "c:\Qt\5.1.1\mingw48_32\lib\Qt5Cored.dll" "c:\Qt\5.1.1\mingw48_32s\lib\Qt5Cored.dll"

Source: Qt5使用静态版，在配置Build&amp;Run环境时，kits项中会出现黄色感叹号

G+ custom url

Got a custom url from g+. You can now visit my g+ page with the following url:

+ZacareshkBlogspotHkLive

Building Qt5.1.1 static failed (Makefile:350: recipe for target 'qfilesystemengine_win.o' failed)

Building Qt5.1.1 failed again. Stopped during creating qmake.

Makefile:350: recipe for target 'qfilesystemengine_win.o' failed
Building qmake failed, return code 2

Building platform:

• Windows Server 2008 R2
• DirectX SDK 2010 June
• MinGW-builds (gcc-4.8.1-dwarf-rev5)
• ActivePerl-5.16.3.1603-MSWin32-x86-296746
• python-3.3.2
• ruby-1.9.3-p448

Building environment:

• DXSDK_DIR=Z:\QtBuild\tools\msdxsdk
• INCLUDE=.;Z:\QtBuild\tools\3rdparty\libicu\include;Z:\QtBuild\tools\3rdparty\openssl\include;Z:\QtBuild\tools\3rdparty\libmysql\include;\include;Z:\QtBuild\tools\msdxsdk\include
• LIB=.;Z:\QtBuild\tools\3rdparty\libicu\lib;Z:\QtBuild\tools\3rdparty\openssl\lib;Z:\QtBuild\tools\3rdparty\libmysql\lib;\lib;Z:\QtBuild\tools\msdxsdk\Lib\x86
• PATH=;Z:\QtBuild\5.1.1\src\qtbase\bin;Z:\QtBuild\5.1.1\src\qtrepotools\bin;Z:\QtBuild\tools\gnuwin32\bin;Z:\QtBuild\tools\mingw-builds\mingw32\bin;Z:\QtBuild\tools\perl\bin;Z:\QtBuild\tools\ruby\bin;Z:\QtBuild\tools\python\bin;Z:\QtBuild\tools\cmake\bin;Z:\QtBuild\tools\utils;Z:\QtBuild\tools\msdxsdk\Utilities\bin\x86;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem

Modify Z:\QtBuild\5.1.1\src\qtbase\mkspecs\win32-g++\qmake.conf:

• from
• QMAKE_LFLAGS            =
• QMAKE_LFLAGS_DLL        = -shared
• to
• QMAKE_LFLAGS            = -static -static-libgcc
• QMAKE_LFLAGS_DLL        = -static -static-libgcc

Configure option:

• cd /d Z:\QtBuild\5.1.1\src\
• Z:\QtBuild\5.1.1\src\configure.bat -confirm-license -opensource -platform win32-g++ -release -static -ltcg -prefix Z:\Qt\5.1.1\mingw481_32s -qt-sql-sqlite -qt-sql-odbc -plugin-sql-sqlite -plugin-sql-odbc -qt-zlib -qt-libpng -qt-libjpeg -opengl desktop -qt-freetype -no-angle -no-qml-debug -nomake tests -nomake examples -skip qtwebkit -icu -openssl-linked -qt-sql-mysql -plugin-sql-mysql -no-vcproj

The error comes out after issuing the configure.bat command. Still searching the solution for this.

Qt configure failed

Using mingw-builds to compile Qt 5.1.1 failed with configure error in configure.bat file. 

./configure.bat: line 1: @echo: command not found
./configure.bat: line 2: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: command not found
./configure.bat: line 3: ::: command not found
./configure.bat: line 4: syntax error near unexpected token `('
./configure.bat: line 4: `:: Copyright (C) 2012 Digia Plc and/or its subsidiary(-ies).'

Really don't understand what's going wrong.
It's time to abolish mingw-builds and follow the official building procedures on Windows.

Solving mingw-builds script download error

Using #mingw-builds to build #Qt, if encounter download error from #http://sf.net , you can download the corresponding file manually and place it inside Qt-builds/work/src/, then create an empty file with <yourDownloadFilename>.marker inside Qt-builds/work/markers/. Re-run ./buildall <yourOptions> will continue the process.

Re-pickup Qt

Start re-pickup #Qt programming. First thing first, I need to compile #Qt with #MinGW #gcc, but it seems a nightmare if I need to have a full set of Qt being compiled with #MinGW.