Some good news, I fixed the fonts by manually creating the font folder and transferring the fonts to the RPI.
In regards to the touchscreen, I ended up observing that the touchscreen worked on the application for the most part. When I use the touchscreen on the app, the touch event occurs in a different location on the interface from where I touched. I want to think that it is a calibration issue but when I exit the application, touchscreen events work as intended. Could it be an issue with EGLFS?
I am still wondering if I need EGLFS to run or if there is a second option that I can explore.
Anyways, I am running v4.19.83-v7+
If your actual declaration is
then it is not an array (of QStrings, I mean), is it, so why do you say it is an array or index it like an array? You tell me what type sendPacket is?
@Surendar-Dharani as mentioned by @maxwell31 regarding libraries, you may want to take a look at step #15 from this guide (I know it's related to cross-compilation, but that step may apply to your issue).
Here is the same post in official forum:
Also here they talk about the same and give guidance about how to do it using cross compilation.
From the posts, the legacy proprietary driver is no more supported on the rpi4.
Currently, mesa drivers are needed for v3d to get acceleration and desktop is needed.
Some one has a an official or standard way to compile Qt for rpi4 to get acceleration?.
Like dependencies and mkspecs.
I'll try a native compilation using mesa and post about it.
If I want to use my application under the Raspberry PIXEL GUI, (lxde using the xcb platform plugin), which GL driver should I use:
Legacy, fake kms or full kms?
And for the raspberry3, which device spec, the pi3-g++ or the pi3-vc4-g++?
I tried with Qt 5.13 and pi3-vc4-g++ and raspian buster, but the result is the same as iwth the pi4 makespec in Qt 5.14
@Stefanoxjx In the company I'm working for we use Qt up to v5.6 for commercial products. We do not use newer versions as those are now LGPLv3 instead of LGPLv2. LGPLv3 requires you to provide the users of your software the possibility to replace (relink) Qt with their own Qt build. This normally requires you to provide object files (*.o) to your users if they ask you to do so. But you do not have to provide source code. So, if you can fulfil LGPLv3 you can use open source Qt version.
@sachinbangadkar_ifm you can't even do that with android studio, 1 architecture =1 apk.
With upcoming Qt versions (5.14) you can make one aab. That basically contains multiple apks.
If you're concerned about the PlayStore, don't be.
Uploading multiple apk's is and will be still possible for a while. Take a look at this blog post for more information:
I reply to myself, just in case some else has the same issue.
Switching the Jenkins build slave from Windows7 to Linux (Debian 10) has reduced the APK build time from 40 minutes to 8 minutes! Yes, my project is relative big ;)
using namespace std;
<< "Lat.: " << qGeoCoord.latitude() << endl
<< "Long.: " << qGeoCoord.longitude() << endl
<< "Alt.: " << qGeoCoord.altitude() << endl;
This is a simple code which i wrote, but the output is just "-nan"
What more should i add to the code?
Hello. It seems I have the same issue. I try to add the Firebace Cloud Messaging to my project, and now after I set v. 5.13.2 my application in some devices is craching at very start. NDK the same as you r19c.
I havent catch how youve solve it? Should I use older NDK (btw it seems that FCM libraries should be compiled with NDK 15 or smth) or can you explain how have you solve it exactly?
@Shiba 's response worked, but for each compile you need do that.
So can put this on <project>.pro to set ENABLE_BITCODE=NO, and it will work every.
Q_ENABLE_BITCODE.name = ENABLE_BITCODE
Q_ENABLE_BITCODE.value = NO
QMAKE_MAC_XCODE_SETTINGS += Q_ENABLE_BITCODE
@jsulm Yes, it works on pc ubuntu 16.04. The qt version on board is 5.9, but 5.12 on pc.
Here is another message sometimes it shows:
[ 13.884117] rockchip-vop ff930000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11
[ 13.919835] [drm:hdmi_config_hdr_infoframe] ERROR Not support DRM Infoframe
the board is connecting an aoc 1080p monitor by hdmi.
I have checked the error msg, it just means no infoframe for hdmi version less then 2.11a, I dont know if this matters, because I can play video to the same monitor correctly.
Sorry I`m new so have to wait 600 seconds to send another text here.