When trying to add an application’s icon yesterday, it failed
whatever hints I tried.
RC_FILE and RES_FILE both failed, no matter what I did…
I am using QT Creator 1.3 and latest qt sdk plus mingw32 as maker.

Finally I found a post to create the res file using the -O coff option.
While before the build process failed with “unrecognized format” on the
res-file, it now suddenly worked like a charme!

So I created an rc file with my app icon, opened a QT prompt, and chdir’ed
to my project’s path. There I did a:
windres -O coff -i appico.rc -o appico.res

In my .pro I added RES_FILE += appico.res.

==> Perfect static build including the application icon.

But there is one thing that I needed to edit in the mkspec win32-g++ in order to make it mingw fully independent, is the parameter:

QMAKE_LFLAGS

I’ve needed to add -static parameter.

QMAKE_LFLAGS = -enable-stdcall-fixup…. [Change it to]-> QMAKE_LFLAGS = -static -enable-stdcall-fixup….

Hope that this helps other people.

The solution for non-standard plugins compiled statically (in my special case this is qico) is like this:

in the .pro add this line:
LIBS += PATH\TO\qt\plugins\imageformats\libqico.a
This is the staically compiled version of qico.

in main.cpp add, like described in this article:
#include
Q_IMPORT_PLUGIN(qico)

This perfectly accesses statically linked icons in the app and displays them as expected.

This opens for me for 100% portable applications with no extra files.

Thank you for your brillant artivle that pushed me into the right direction!

Not having the slightest idea, what I am doing there (lol, well almost no idea), I modified my .pro with this line (having QT completely static):
QTPLUGINS += libqico
After all I already have that static versions of the plugins, libqico.a and libqicod.a. It compiled errorfree, however Icons on toolbar buttons still are not displayed.

nucrash :I stand corrected.. HTML 5 is more of in an Alpha Stage: http://en.wikipedia.org/wiki/HTML_5
They still are developing pieces of it and throwing in features at the last minute. I would assume it will be in Beta later this year.

There is no “beta” or “alpha” or whatever with HTML 5. Many of the feature in it (such as ) were actually in browsers before work on the standard even started. The standard process in this case is to take a look at the landscape, find what’s working and what’s not working, and to write a standard that describes the good stuff and try to correct the bad. Some browsers (Chrome, Firefox, and Safari) are adding in HTML 5 functionality as it comes. IE, with its release cycles geared towards huge leaps in functionality every few years (instead of the iterative approach) won’t have much HTML 5 functionality until version 9.

The HTML 5 spec is currently on track to reach “Last Call” status in a year. It cannot become a W3C “recommendation” until there are 2 100% complete and compliant implementations of it out there, which is estimated to be arouns 2022. Everyone throws a temper tantrum about that number, but the reality is, HTML 4 does not meet that metric yet, and it has been out for over 10 years!

J.Ja

They still are developing pieces of it and throwing in features at the last minute. I would assume it will be in Beta later this year.