QtonPi

Great, thanks for sharing the solution!

Regarding QFtp..

I've been wanting to use it because I hate using time/money on something that already is provided.
In total with learning how to build it, and building it for several platforms and failing on some, I guess I have used about 30 hours of work time plus..

Today I just got to fed up with not getting it right for the raspberry platform and decided to give writing my own a shot, since I've already built a few other protocols from RFC.. And very glad I did, as I've already got the connections up and running with both control and datachannel.

Just 4 hours in, I can do everything I wanted to do with QFtp xD Guess wanting to be the most effective made me very uneffective in this case :p

@JackTr

You need to give more specific information on your actual issue with cross-compiling.

"Missing EGLFS Fix

On recent versions of Qt (e.g. 5.10.1), the qmake.conf file for linux-rasp-pi3-g++ doesn't work, however, linux-rasp-pi-g++ does. Create a new qmake.conf based on linux-rasp-pi-g++ with the build flags from the Pi 3 spec copied over.

Another fix is the replacement of the broken lines:

VC_LIBRARY_PATH = $$[QT_SYSROOT]/opt/vc/lib
VC_INCLUDE_PATH = $$[QT_SYSROOT]/opt/vc/include
VC_LINK_LINE = -L$${VC_LIBRARY_PATH}
QMAKE_LIBDIR_OPENGL_ES2 = $${VC_LIBRARY_PATH}"

Found this on the wiki site, I tried to replace the broken links before I found it, that did not work, but it also says here to build with rasp-pi instead of rasp-pi3 so I'll try that.

That did not work still the same error...

The idea is that you try playing your video using the GStreamer command line tool as GStreamer is used as backend on Linux for multimedia related stuff.

@Sencis said in Install QT 5.13.0 on Tinker Board without Cross:

The solution was to reconfigure as follows:

./configure -platform linux-tinkerboard-g++ -eglfs -qpa eglfs -release -opengl es2 -nomake tests -nomake examples -opensource -confirm-license -v

And although the HelloGL2 / 3 examples now work fine, when the application starts (and it always runs on the full screen), the X server stops (or minimizes), you have to exit the system and run it in terminal manually. Perhaps this is fixable, but use it with VNC not possible. Also the frame rate in example HelloGL3 quite small. Perhaps the performance can be increased on this board by increasing the GPU frequency in the board settings (You can find the topic on the forum of this board how to do this) but apparently the automatic frequency control does not work here which will probably lead to more power consumption and heating.

Hey, going to have a project with same Tinkerboard. You said the animations weren't really smooth. Did you make it working with better frame rate?

@jsulm Thank you very much.Let me try...

@PatZim said in RaspberryPi2EGLFS tutorial fail at Step 10 "./configure":

I am wondering if there is no native solution for Macs

As you figured out yourself, I guess it all just comes down to get a cross-compiler for ARM that runs on Mac...

But I bet using the VM with Linux is a good approach, given that lots of guides/tutorials are based on such platform

@jsulm Thank you! That seems to have resolved my problem.

@Pablo-J-Rogina as a follow-up, it looks like my plan with ArchlinuxARM failed.

After installing Qt libraries (and dependencies) on the target, and rsync'ng the sysroot on the host, I was not able to create a proper kit in Qt Creator since there's no qmake that runs on host but refers to cross-compiling settings.

Before moving back to actually cross-compiling Qt libraries, I guess I'll attempt another approach:

Install pre-built Qt libraries on target Install distcc and cross-compile toolchain in host Not sure if I need a sysroot on host Still not sure how to set the kit in Qt Creator (since the qmake exe will be in target anyway)

Actually it's the other way around. To use effectively the programmer has to learn a lot. Far too often kiddies think they can read a few samples and then design full professional Qt applications. There is a real and substantial time investment in learning the Qt framework.

@tenrisab4o It seems there's no URL to follow from your post...

@Fernando-Melo

Hi,

just build a cross compile for Raspi.

I ran into the same problem with 5.11.3 what is old, but comes with Raspi 4.

Your receipe solved this, but no root has been required.

I ran:

WORK=$PWD
cd ./qtlocation/src/3rdparty/clip2tri; make ; cd $WORK
cd ./qtlocation/src/3rdparty/clipper; make ; cd $WORK
cd ./qtlocation/src/3rdparty/poly2tri; make ; cd $WORK

Beside that. There are other compile issues related to incompatiblty.

I skipped them by skipping the problem modules by adding this to confguire:

-skip qtwayland -skip qtlocation -skip qtscript

(thanks to: https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/)

Marko

The window manager is free to ignore whatever it wants to ignore. As the name suggests these flags are hints.

One thing you should check is whether you can have a kiosk mode enabled so that you can have some sort of single application interface.

@barath-19-2 I asked before: "And it looks like you're not doing cross-compalation?"
So, are you doing cross-compilation?
The wiringPi library is apparently not compatible with your platform.
If you build on your PC/Laptop for Raspberry Pi you have to do cross compilation as Raspberry Pi is ARM and not x86.
So, did you set up a cross compilation environment?