Cross-compiling QT5.7 for linux ARM setting linker path

SGaist

Hi and welcome to devnet,

What options are you passing to your configure call ?

Note that if your device is like a BBB, you should use the BBB mkspec as a base for yours and pass the proper information to configure.

SimonB

BASE_DIR=$(pwd)
TOOLCHAIN_DIR=$BASE_DIR/../toolchain/arm-cortex_a8-linux-gnueabi
HOST_TYPE=arm-cortex_a8-linux-gnueabi
SYSROOT_DIR=$BASE_DIR/../toolchain/arm-cortex_a8-linux-gnueabi/arm-cortex_a8-linux-gnueabi/sysroot
TARGET_DIR=$BASE_DIR/../buildroot/board/tornatech/filesystem/opt
PREFIX='qt-embedded'
EXTPREFIX=$TARGET_DIR/$PREFIX


CONFIGURE_CMD="./configure -v -xplatform linux-arm-gnueabi-g++ -device linux-brio-tor019-++ -sysroot $SYSROOT_DIR -extprefix $EXTPREFIX -device-option COSS_COMPILE=$TOOLCHAIN_DIR/bin/$HOST_TYPE- -make libs -confirm-license -release -opensource -force-pkg-config -no-icu -no-dbus -no-xcb -no-gif -no-xkbcommon-evdev -no-evdev -tslib -no-mtdev -qt-libjpeg -qt-zlib -no-harfbuzz -no-libproxy -no-xinput2 -no-xcb-xlib -no-pulseaudio -no-alsa -no-largefile -no-iconv -no-pch -no-sse2 -no-glib -no-cups -rpath "

The "device" stated here exist, that's the name of our folder containing the qmake file. My example for the qconf ( in mkspec ) was the beagleboard, the file is almost identical to the beagleboard one, except for the soft floating point

SimonB

Actually, I have to revise my question.
qmake is able to be built, but at the runtime when I try to launch the QT compilation, it ask for

/lib/ld-linux.so.3: No such file or directory

jsulm

@SimonB What does

ldd qmake

say?

SimonB

This post is deleted!

SimonB

@jsulm
It says :

        not a dynamic executable

I guess I am missing a flag or something at compile time, I tried a lot of combinaison for including my "fakeroot" folder. I tought that it was the point of having --sysroot in the configure script

SGaist

What do you get if your call file qmake ?

SimonB

@SGaist - Thanks for your quick reply

qmake: ERROR: cannot open `qmake' (No such file or directory)

I am still looking for a "missing flag" in the conf file ... is there anywhere else I should look ?

I just had a tought,
I want to cross-compile QT to have the libraries on my embedded platform. Am I doing this wrong by building qmake with the cross-compiler app ?
since qmake is used to build the makefile for QT, I have to run it on my host system right ? So, that being said, do I need to have qmake cross-compiled ? sor sure it won't work on my system

my reference was :
Building Qt for Embedded Linux
but it says that this is obsolete and it's only good for QT4, I bet this is good for QT5 as well ??

( This is my first time compiling QT )

SGaist

Ok... When someone suggest to call ldd on a file, you are supposed to give the full path that file or change your current folder to where that file is otherwise the command won't work. The same for file.

As for your qmake.conf i'd remove the QT_SYSROOT assignment, it should be done for you through the configure script and the parameters you give it.

qmake is a host tool that is not cross-compiled.

SimonB

The file and ldd worked, but the binary was a arm compiled binary, that's why it wasn't working. May I suggest updating the http://wiki.qt.io/Building_Qt_for_Embedded_Linux#The_Host_Build to specify that it's still the actual way to to it, even in qt5

@SGaist said in Cross-compiling QT5.7 for linux ARM setting linker path:

qmake is a host tool that is not cross-compiled.

I figured that out today !! I am still wondering why it is trying to compile qmake with the cross compiler when I make the second configure ( the one with the option -device CROSSC_COMPILE= ....

SGaist

Are you doing your second call to configure in a clean state ?

SGaist

The article you mention is really specific to Qt 4. So no, it should not be modified. There's even a link at the top for Qt 5.