@abhisit said in How to debug / backtrace the call stack?:

Can I use try...catch() like below code?

No, there is not even a try block in that code and you can't put main() call into a try block as it is called by the loader of the OS, not by you.
You can't use exceptions to catch segmentation faults. You need to run a debug build of your app to see where exactly it crashes.

AFAIK, the BPI is very close to the Raspberry Pi, you should take a look at this wiki entry.

By the way, why are you trying to build an outdated version of Qt ? The current LTS is the 5.9 series with 5.12 around the corner.

@SGaist

Thanks for the reply. Indeed you are wright. It is very easy actually. I just compiled qt4.8.6 for my system. Then I found the sqlite project in sqldrivers. Compiled this library for my system, copied it and it works!

Very easy. Learned again a lot!
Thank you all for the great support!

Just case: the latest version of Qt 4 is Qt 4.8.7.

@Pablo-J.-Rogina
Thanks for the time to make example code.
It didn't work straight away, this because I use qt4.8 and you the newer one probably.
So I changed your code to the older syntax to get it working.

I would like to thank you and all others for there help!
Again I learned a lot!

Thanks for helping!

@TMJJ001 I would not run this software on your PC - how would it communicate over canbus?
Instead you can provide the possibility to connect to this software (server) over network and then write client software for your PC which connects to your server software on the embedded device.

@jsulm

Sorry for the late reply.
There was an error in the .xml file and not in my code!
So I managed to solve the error.

Code works like a charm!

The solution to that problem is to insert the following call to the constructor of the file processing class:

QTextCodec::setCodecForLocale(QTextCodec::codecForName("UTF-8"));

Concerning the shell:
I use BusyBox (its light) which doesn't provide locale and the environment variables like LANG=en_US.UTF-8.
For compiling BusyBox configurations can or have to be given containing

CONFIG_LAST_SUPPORTED_WCHAR=0

the number is the last displayable number of the Unicode list, 0 signifies that all characters shall be displayed, it was set to 767 which includes west European characters. The excluded characters are replaced by the character defined in the same configs, in my case it is "?".

Because QWS is Qt 4 only.

You can vote here: https://bugreports.qt.io/browse/QTBUG-58964
I hope that Qt developers solve this issue.

@Antonio-Ortiz

I am glad to see that you could solve your problem.

The wildcard option is quite helpful, but also quite dangerous, if you are not very careful.

I have the same problem, did you resolve it?

@develop-it See my answer here: http://forum.qt.io/topic/68325/the-library-could-not-be-configured-for-supporting-multi-threaded-applications
If you have another error while executing make then you should post it here, else it is not possible to help you.

To complete, i tried to configure the settings and i have the output of the cross compile who say me TERM environment variable not set.
The cross compile is now standing something, but i don't know what because i've already set my TERM environnement → /usr/bin/xterm -e

Thanks.

Having the same problem with a cross-compilation using the linary toolchain (aarch64-linux-gnu-) v6.2.1

error: 'EGLNativePixmapType' has not been declared

Did you manage to find what the problem was?

Solved: Now I use wayland-egl and everything is fine.

The Long Story to Get the Simple Solution:
At first, I used raspberrypi-userland for OpenGL ES. However, it didn't work.

I tried VC4 DRM driver in the next. I have struggled to get it work, and I opened an issue on the repository. Then anholt, the author of the driver,
updated the Wiki. By following the Wiki, I finally succeeded in getting it work.

mesa3d is necessary to provide OpenGL ES API, so I installed it with drm backend. However, it didn't work since eglCreatePbufferSurface is stubbed in the backend. So I had to use other QPA.

Next, I tried X11 since Buildroot supports xcb backend, but neither did it work. I thought porting Wayland should be much easier than fixing the issue, and actually it is.

Hi,

Isn't that the same question as you asked here ?

I am having this exact problem. I compiled my project for an embedded arm device, linux desktop, and windows desktop. The windows and linux hosts display the characters correctly, where the embedded device just shows nothing.

I'm using the Noto fonts https://www.google.com/get/noto/#sans-hans and am positive it is being used on the linux desktop, since if I don't copy the font into the same directory as the application, it just shows blocks. When the font is in the directory, it shows everything properly.

I tried the same thing with the embedded build, and nothing shows up. The font being loaded, since if it's not in the directory, it complains that it can't load it. Is there some extra switch or rendering tool/application that embedded linux needs? I've tried with both 'linuxfb' and 'egl' platforms with no success.

Thanks in advance for any help.

Ok I see now, that when I configure with toolchain for armbcm from raspbian, it fails, but not because of the compiler ( make goes much further). I will search for another toolchain. I'm curious if the application made by such configured and built qtbase (with previously mentioned armbcm toolchain) will work on Banana.

Now only I have to eliminate the problem with qt ide remote connection
(error "Server sent invalid f"). If anybody knew how, it would be a blessing for me.

Good, then please mark the thread as solved using the "Topic Tool" button so other forum users may know a solution has been found :)

My log also include the message: This plugin does not support setParent!

Please advise!
IL

I am able to compile a Hello world cpp code and generated binary file is successfully running on my board.

@SGaist thank you for the fast reply. now I started to see the difference.

Hi

May I ask how you got this to build?

I am trying to compile Qt with the following configuration (for Raspberry Pi):

./configure --prefix=/usr -release -opensource -confirm-license -c++11 -no-largefile -no-qml-debug -system-zlib \ -no-journald -system-libpng -system-freetype -system-libjpeg -system-sqlite -openssl -no-pulseaudio -alsa \ -no-sql-db2 -no-sql-ibase -no-sql-mysql -no-sql-oci -no-sql-odbc -no-sql-psql -no-sql-sqlite2 -no-sql-tds -nomake examples -reduce-exports \ -no-directfb -no-linuxfb -eglfs -no-xcb -device linux-rasp-pi-g++ -device-option CROSS_COMPILE=/usr/bin/ -sysroot /

Here is my patch:

diff --git a/qtwebengine/tools/qmake/mkspecs/features/functions.prf b/qtwebengine/tools/qmake/mkspecs/features/functions.prf index ef0320d..5abaecc 100644 --- a/qtwebengine/tools/qmake/mkspecs/features/functions.prf +++ b/qtwebengine/tools/qmake/mkspecs/features/functions.prf @@ -12,13 +12,9 @@ defineTest(isPlatformSupported) { return(false) } - linux-g++*:!isGCCVersionSupported(): return(false) - !isPythonVersionSupported(): return(false) - linux-g++*|win32-msvc2013|macx-clang: return(true) boot2qt: return(true) - skipBuild("Qt WebEngine can currently only be built for Linux (GCC), Windows (MSVC 2013), OS X (XCode 5.1+) or Qt for Device Creation.") - return(false) + return(true) } defineTest(isPythonVersionSupported) { -- 2.1.0

And it succeeds, but I don't get a message about WebEngine being an unsupported platform. It simply does not build that module. I tried to follow this reference here, but had no luck either: https://forum.qt.io/topic/48223/webengine-raspberry-pi/2

I am building native, not cross, on Debian Jessie.

Thanks in advance,

Sam

Or use QMapControl and customize it :) , Qt mobility and merbal both are sound fine to me thanks guys I will read more about them ...

Its ugly workaround, but can helps.

Open your <EGL/eglplatform.h> in text editor and after strings:
#include <X11/Xlib.h>
#include <X11/Xutil.h>

add following strings:
#undef None
#undef CursorShape

Yes, better to make clean build

Hi and welcome to devnet,

If possible, you should upgrade to 5.5, IIRC, there's been a lot of work done in the bluetooth module for it.

I find the reason:
in these way this error occurred :
1- the permission of file : the output of tslib should has full permission :chmod -R 777 /.../.../tslib
2- the address of tslib is wrong. if you write wrong address this error display
3-if you install tslib successfully , and then remove it and install it gain this error show you. i change my linux and install another one but should clean all the tslib file and details.

Hi and welcome to devnet,

Which version of Qt are you trying to build ?

@SGaist Thank you for your suggestion. I would like to know anyone particularly used Qt for Electronic paper Display. If yes, then I would like to get the difference if any.
I believe the users can give suggestion.
Meanwhile, I will post the same in interest mailing list also.

Just checked the code of FlickCharm, it does not touch the paintEvent so it looks like what you want, no ?

Hi LuGRU and ambershark,

Thank you very much for the information. I will look at them and pay attention to their license requirement.