Installation and Deployment

Hi, Did you also compile the Qt plugin ?

Hi, You should not install Qt in /usr/bin. The default is either the home folder or the /opt folder. Unless you're on a shared computer where several people are going to use Qt, you should install it in your home folder.

@jsulm I just upgraded to 18.04 (a rather nightmarish experience, and still the DNS is not set automatically), and then I followed your advice to remove Qt directories from the PATH. That fixed the uic problem. I have two versions of Qt Creator, one that I installed (Qt 5.13.0) the other I think automatically installed by Ubuntu (Qt 5.9.5). I have to use the 5.13.0 version, because if I use 5.9.5, uic only works with Qt 5.9.5, which lacks some recent features I need. So many thanks for all your help. Gib

@sokhanh21xn I do not see any of your attachment or sample code. You can refer this for more details.

hey guys this problem has been solved by installing qt 5.13 with Installer. Additionally just clone emsdk from git and follow instructions in qt documentation. Now I can compile and run in Browser. But still its a bit problematic with qt cause you just cant run from qt. Hope that the release comes soon to build directly from Qt I wanted to ask you guys a question in relation to qt configuring kits. The webassembly kit it could not find any ABI and that qml scene is not installed. Its a warning but I can still do qmake and make and run the project in the browser.

Hi and welcome to devnet, What version of the MySQL libraries do you have ? Where exactly are they stored on your machine ?

@jsulm But qmake doesn't fail when I do Build > Run qmake, and the build does succeed. I've now found that if I build for the first time then close the project (no project tree), then reopen the project, I do get a project tree. You might not call this a bug, but it's definitely confusing and undesirable. There is also the issue that after a successful build, clicking the green arrow to run the program gives the "Could not find the executable" popup. (I just discovered that on reopening the project - and seeing a project tree - the green arrow does execute the program.) It seems likely that all these issues stem from the same cause. Yes, this is all within Qt Creator.

@gibbogle Click on "Topic Tools" at the bottom and then "Mark as solved".

@sgaist There does not seem to be any discernible environment-related reason as to why this happens on some systems and not others. I have created a new bug report https://bugreports.qt.io/projects/QTBUG/issues/QTBUG-78146 Clive

[image: 76eb5c40-4e61-4b6b-ae89-0ce60cf6bd0e.png] I have these versions . It does not work when i build directly on raspberry pi .

Hi it seems to be an ABI warning. If both your toolchain, Qt version and your app is compiled with the same compiler (aka version), it should be ok to ignore. The warning can be disabled with -Wno-psabi However, please read a bit about it before just using it. https://stackoverflow.com/questions/52020305/what-exactly-does-gccs-wpsabi-option-do-what-are-the-implications-of-supressi

Thank you

Hi and welcome to devnet, What version of PySide2 ? What version of Python ? What version of Qt Creator ? What OS ? How did you install them ? What code are you talking about ?

@sujay I've read your post, and maybe this error is related to opengl/es. Did you enabled this feature in yocto? Also which platform (hardware) do you use? Maybe it will be better to switch from linuxfb to eglfs.

You're welcome ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :-)

@alipanahi2 said in why qt dont create .deb for ubuntu: thank you, is that for one case? any other reason there is? Another reason is ease of maintenance - there is ONE installer, not dozens of DEB and RPM packages for each distribution. Yet another reason - installer allows you to install locally (for current user only), without root access. And finally - installation to /usr/ would cause Qt debug libraries to be in system search paths. Apps in your OS might then run with them instead of release ones. Also, this is another issue - distribution usually builds all apps against single Qt version (sometimes with custom patches applied!), and it may be different from one you want to install. So it could happen that you installed new Qt version into /usr and suddenly your apps stop working.

@sgaist Have you been doing what I am asking about? Have you been deleting what you are writing about? Is there ability to exclude driver when application built and deployed on device? I know in precise that it should be defined before deploying and build but I don't remember how.