@kshegunov Thank you! That was the missing part!!

@SGaist no, I did not. I just tried it with --qmldir specified and it worked flawlessly. Lesson learnt. However, I feel the deployment article could be a little more informative.
I appreciate the help!

Here you have the instructions

@oberluz
No problem, although the merit should go to @SGaist who actually sensed what the problem is. :)
Cheers!

@Gagiopapinni
Okay, can you verify that this symbol is present in the static lib? (you could use "dependency walker" for that purpose)

For the recored, filed QTBUG-53845

when the window inactive, just raise it

onActiveChanged:{
if(!rootWin.active){
rootWin.raise()
console.log("rootWin raise")
}
}

Hi,

QtWebKit for Android and iOS ? Highly unlikely, since both platform forbids the use of non-native web views and there was no ports.

Taking a quick look at the QtWebView module, there's a QtWebEngine backed WebView when that module is available. So currently you should be able to use that module on all the platforms you are interested in provided that you use a compiler that is supported by QtWebEngine. Note that the compiler constraint doesn't come from Qt but from the Chromium project.

@alex_malyu

Thank you for the ideas. I will keep this in mind.

@pavel_abr Did you solve this? Please let me know the solution.

Hi @asthana-ujjwal and welcome to devnet,

Can you show your .pro file ?

@oblivioncth said:
Ok, its shaping up , super :)

"Helps givez me codes".

We do help those too but good questions often get better answers.
Also its clear that you do try to fix it first yourself, so some holes in c++ is no issue.

Cheers

@SGaist Thx I will give it a try.

I am closing it as solved since the issue has been reported for bug-fixing and there are other options to make it work.

Hi,

Qt3D being currently a tech preview, I'd recommend posting this question on the interest mailing list You'll find there Qt3D developers/maintainers (this forum is more user oriented)

Hi. I've been thinking about this for a while and I have no idea... I don't think it's related to your gcc version. If you don't need this module, you could skip it.

-skip qttranslations