Installation and Deployment

I was hoping that someone have tried that, or knows more details. Anyway, thank you for directions, I'll try the mailing list later ;)

I see. It is uncomon to see a single header being named a library. I am not familiar with it. I suspect you need to first compile that into a library, and then include that library in your source code. But maybe it is intended to work in a different way.

please if any one can help me

Well, how silly of me. But ofcourse you have to install it as root. Although it seems like it might be installed in any directory of your choice, on my system it defaults to /opt. I never gave this a thought, since I always install apps as root. So it did not occur to me to hint this as a solution I'm glad you figured it out though.

The -I option for configure indeed works; sadly the mingw headers (Ubuntu 14.04 deb) explicitly fail compilation if the target isn't Win32 so rather than burn more time on this, I'll look at switching the offending tools to cross compile. I'm far from certain what the expected target is for the Qt tools when cross compiling; should SDK bundled tools build for the host or target?

I guess I'll just have to wait him, and see if he did some wizardry on how to build it. Thanks for the quick answers anyway! =)

Ok, now works. I needed to install Mesa-libGL1

I am not a lawyer so for licensing issues you should either contact one or talk with Digia directly. Yes, you'll only have a dependency on VS runtime but it's normal and it's better to keep it so.

I forgot, yes it does support Android. However AFAIK, Qt Creator won't show you templates for platforms you don't have kits for.

Please Can someone help me?

Hi, IIRC yes it is

My bad, I didn't realize it was only the sources. That should be mention in the link name.

Perhaps you need to additionally install libqtsvg, then. Ubuntu packages all Qt modules separately.

You should not use stable but 5.3 (until 5.4 is out)

This bug has been reported https://bugreports.qt-project.org/browse/QTBUG-39859 For now they found another workaround which doesn't involve changing any file: simply install libEGL-dev. (e.g with linux MINT the package libegl1-mesa-dev avoid the error).