Mobile and Embedded

Hi MMMartin, It does look like you need to install the desktop MSVC2017 64 bit kit in order for the QT for MCU kit to compile. It would have helped if the install instructions in getting started with Qt for MCU video would have identified what components of Qt need to be installed if only Qt for MCU is desired, and not the entire Qt software, which is a huge install. The need for this is shown in the video at 13:00. Hope this helps, -onlyMCU

compile QtQuick.Controls 2 from source solve this problem?

Thanks, ( I have installed Qt5.14.1 and changed the Sdk to 26.x.x)

@JoeF Hi, given that Boot2Qt is now Qt for Device Creation, and that component needs a commercial license, wouldn't you get better support from Qt directly? This is a community-driven forum

Up topic.......

Looks like there's a bug somewhere in the lower levels of your system. Do you get the same result if you plug your mouse in another port ? Do you get the same result if you plug a different mouse in the same port ? You likely don't have that file available anymore when the device restarts, do you ?

@Ashishx88 said in QT 5.9.8 declarative fails to compile with "-no-opengl": Is there any way / mechanism / tool by which we can determine such dependencies for required modules. I checked the qtdeclarative recipe DEPENDS macro but could not see any dependency for opengl mentioned there. Hence can you let me know if there is any standard way to determine such dependency . I'm not aware of any tool for checking such dependencies, but this documentation is a good place to start https://wiki.qt.io/Building_Qt_5_from_Git In a nutshell, qtdeclarative.git contains Qt's most advanced graphics features. In the past, OpenGL was the obvious choice for implementing cross-platform graphics -- that's why OpenGL is a hard dependency. However, more backends have become available recently so from Qt 6 onwards, OpenGL will become optional.

Turns out when i remove mediaContainer in videoRecorder properties it works. The video format default will be .mov . So the problem is the format plugins

Hey, Just wondering if you found any solution to this?

@Pablo-J-Rogina said in Rasp Pi Cross Compiling not working as expected: Please explain this a little bit more. Are you deploying and running the application from Qt Creator on Linux? I'm deploying the application from QtCreator on Linux and running it on the Raspberry Pi. The main issue is based on a numeric keyboard I designed to allow input from users using a touchscreen, the keyboard is a dialog that appears on top of the parent when a textedit is focused. This stops working when I follow these steps: Cross compile and deploy from the Linux computer to Raspberry Pi. The application automatically starts on the Raspberry Pi. I test the application without closing it. (works as expected) Reset the raspberry Pi and re-open the application directly on the Pi. The application behaves differently, the dialog is shown behind the parent dialog and not in front. Other smaller issues appear, p.e. the design of the warnings dialogs are different. I'll upload pictures later today showing the issue. Again, please explain a little bit more. How are you starting your application? from command line? Is it using X11 or EGLFS or Wayland? I'm a noob regarding these issuses. I've followed these tutorial: https://wiki.qt.io/RaspberryPi2EGLFS https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/ So I guess it is EGLFS. Again, Thank you!

Well it's an analytics portal for displaying information such as user accounts, sales, as as well to configure some parts of the app and embedded machines remotely. We have SSL, I thought that as long as the traffic is encrypted, we have brute-force penetration protection and don't use the root login, there shouldn't any security issues as long as it's configured correctly? I'll have to start looking at APIs such as REST, are there any additional steps to configure these APIs with Qt, or do they work out-of-the-box with QML? Thanks for the information! Ryan

@SMEG In the article you link there is a link to whole source code of that example project: https://github.com/KDAB/android

Hello! I met the same error. Have you solved it?

@SGaist Hello, configurating with -kms fails. When installing libdrm-dev, it adds header files into this path: sysroot/usr/include/libdrm/ while the file xf86drmMode.h is trying to include <drm.h>, but is in this path sysroot/usr/include/ Do i have to manually add sysroot/usr/include/libdrm/ as an include path before configurating Qt, so that xf86drmMode.h can find the <drm.h> which is in the subdirectory libdrm?

I have similar issues trying to create / use an avd. QT creator keeps telling me it cannot create an avd while android studio runs them fine.

@J-Hilk Thanks man, your answer saved my time also, I had Qt 5.13.1 and serial read was not working, I updated to 5.14.0 and now it works.

So thinking about the QtNetworkAuth module ?