@lx_frz said in How to get cross compile toolchain from target system:
Switching to 5.9 helped.
I think I have just one more problem before this will work.
When I built the 5.9 and made an executable, it was recognized on the target platform, but couldnt run because it couldnt find the Qt .so files, despite them being on my platform.
I had that problem too, but this helped
export LD_LIBRARY_PATH=/home/ubuntu/QtForBBB/lib:.
The statement above is basically similar for that case as the path enviroment setting in windows.
The only issue is, for windows boys like me, the different syntax to separate path values. The separator is a ' : '
The shared libraries are on QtForBBB/lib and the default folder ' . ' for the dynamic libs of my application. Basically the default is also the folder where the application executable resides. linux does apparently/obviously not look into the default folder for dynamic libs.
On some threads I found from google, it qas recommended that I compile Qt statically to avoid this. I tried it and it worked. However, there is still 1 missing .so, libstdc++.so.6
I have seen those posts in the past as well, but actually I was surprised how easy this dynamic link part.
Supposedly I could use the -static_runtime option to statically include this, but when I try that I get
Warning: Feature static_runtime is insignificant in this configuration, ignoring related command(s)
So I can make executables now, but they wont run on my target because I cant compile with a static libstdc++.so.6
libstdc++.so.6 is part of the compiler. On my BBB it is found on folder /usr/lib/arm-linux-gnueabihf
As the whole setup looks to me is the compiler with all its libraries already installed on the device. Probably it came already with the bootable SD card.
For you that would mean that you need to install the gnu c++ with its libraries.
