Installation and Deployment

If you are opening a project configured on another computer you might have a myproject.pro.user file that might not be usable on your computer. Close the project, remove that file and open your project again to reconfigure it.

I dont know what helped me but I ... ran "run make install" in qtbase dir removed "Qt 5 for Raspberry Pi" and installed the path again, then it was recogniced right as Qt for Embedded Linux.

thanks a lot fellas ! problem solved , actually my source file was having .c extension i changed it to .cpp and it worked !

Just got it working! Apparently I was using a cygwin version of make, as opposed to mingw32-make. Thanks so much for your help!

You're welcome. :) Please don't apologize; this is a normal part of learning! Good luck. If you have any more questions, please ask. We would be happy to help you.

[quote author="clochydd" date="1394294174"]Hello and welcome to devnet, do you have a selected version in "Qt Versions" and a Kit selected under "Kits"? [/quote] Thank you for your reply. After reading your post, I looked at the section of "QT Versions" and I saw this: !http://oi57.tinypic.com/j82pli.jpg(QT Versions)! So I googled "msvc 2012" and found out that I was needed the Visual Studio 2012. Just installed it and it works! :) Thank you again.

Were you ever able to get this running?

Once you have a deployed application i.e. get it running properly outside Qt Creator, you need to choose an installer builder either QIF, InnoSetup or NSIS (other exists) to create an installer that will handle that.

So it turns out the issue was Avast antivirus's realtime protection. Thanks again for all the replies.

Hi and welcome to devnet, Looks like your are trying to cross-compile your application using a x86 Qt. Did you also cross-compile Qt first ?

I'm sure it's not. The actual process does not intimidate me. Nor does the fact that Qt involves its own dialect of C++; so suddenly we're locked into the Qt motif, when maybe all we're interested in is basically fancier language standards.

I can believe that to fix this issue, I just need to re-name my package as "com.whatnever.myAPP", thanks Genonn

Sorry, lucaghera, I cannot see what's going wrong. Hopefully someone else had a similiar isssue and may assist with that.

Were you ever able to get it working? Only clue I found was a comment here that static build isn't supported yet for Qt Android: https://bugreports.qt-project.org/browse/QTBUG-36097

Using Qt 5.2.1 on OS 10.8.5 I was getting the same error. To resolve it I was able to clone the clang Kit and select the lldb debugger. lldb seems to be working now.

Hi and welcome to devnet, What part of your code generates that error ?