How to use qmake to cross-compile for imx6?
-
wrote on 17 Mar 2017, 15:28 last edited by
-
What cross-compiler are you using ?
-
wrote on 17 Mar 2017, 21:13 last edited by
The tools that i use:
- Qt 5.8.0.
- Qt creator 4.2.1
- Poky linux 2.0.3.
-
Good to know, however that doesn't answer the question about the cross-compiler version.
-
wrote on 17 Mar 2017, 23:29 last edited by Alexander-9
For the cross-compiler i use toolchain the next : poky-glibc-x86_64-meta-toolchain-qt-armv5e-toolchain-qt-2.0.3.sh, i am in the correct??.
after of install some packages, i can run ./configure https://drive.google.com/file/d/0B66wEl1-cjbObjJEY1pYd3lkTU0/view?usp=sharing.
but in the moment that run make, show me the next error https://drive.google.com/file/d/0B66wEl1-cjbOOUQ4NzBkRDBORTg/view?usp=sharing.
or what is the error i am making??, regards
-
From what you wrote you try to use a toolchain that is for ARMv5, the imx6 AFAIK, runs on an ARMv7 so I'd say no that won't do it.
Also, please translate the error message.
-
From what you wrote you try to use a toolchain that is for ARMv5, the imx6 AFAIK, runs on an ARMv7 so I'd say no that won't do it.
Also, please translate the error message.
wrote on 22 Mar 2017, 00:14 last edited by@SGaist, Hi i can run ./configure and if create the qmake, but the qmake that create is for x64 and this is what i don't want, i have that add other thing else, for that can create a qmake for ARM.
Regards.
-
@SGaist, Hi i can run ./configure and if create the qmake, but the qmake that create is for x64 and this is what i don't want, i have that add other thing else, for that can create a qmake for ARM.
Regards.
@Alexander-9 You need to cross-compile for your target. You can see how it is done for Raspberry Pi here http://wiki.qt.io/RaspberryPi_Beginners_Guide (don't know what your target device is, but it will be similar).
-
To add to @jsulm, that's normal. When cross-compiling there are host tools like qmake that will be built for your desktop machine so your can develop on said machine while targeting your device.
If you want build your application directly on your target then you'll have to do a native Qt build on your target also.
-
wrote on 22 Mar 2017, 17:02 last edited by Alexander-9
@jsulm , @SGaist I intented run of cross-compiler with next way:
./configure -release -opengl es2 -device linux-imx6-g++ -device-option CROSS_COMPILE=/opt/poky/2.0/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi- -opensource -confirm-license -prefix /opt/imx6, this way of cross-compile is correct??
But show me this ERROR: Cannot compile a minimal program. The toolchain or QMakeSpec is broken., and for details Config.log, in this moment i'm seraching the way for add the files crt1.o, crti.o etc, etc, regards.
-
You are at least missing the
sysroot
option. -
wrote on 22 Mar 2017, 22:57 last edited by
@SGaist Excuse fro the question, but sysroot what is??
-
@SGaist Excuse fro the question, but sysroot what is??
@Alexander-9 Sysroot is a directory containing the content of the target device file system (or parts of it). It must contain all needed header files and libraries from your target device, else you cannot cross-compile.
-
wrote on 23 Mar 2017, 16:42 last edited by Alexander-9
@jsulm, @SGaist , this the new cross-compile: ./configure -release -opengl es2 -device linux-imx6-g++ -device-option CROSS_COMPILE=/opt/poky/2.0/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi- -sysroot /dev/sdd -opensource -confirm-license -prefix /opt/imx6, is correct this??
after of run the configure, show me in the Config.log:
executing config test verifyspec
- cd /home/qt/Descargas/qt5/qtbase/config.tests/common/verifyspec && /home/qt/Descargas/qt5/qtbase/bin/qmake -qtconf /home/qt/Descargas/qt5/qtbase/bin/qt.conf "CONFIG -= qt debug_and_release app_bundle lib_bundle" "CONFIG += shared console" "QMAKE_CFLAGS += --sysroot=/dev/sdd" "QMAKE_CXXFLAGS += --sysroot=/dev/sdd" "QMAKE_LFLAGS += --sysroot=/dev/sdd" /home/qt/Descargas/qt5/qtbase/config.tests/common/verifyspec
- cd /home/qt/Descargas/qt5/qtbase/config.tests/common/verifyspec && MAKEFLAGS= /usr/bin/make clean && MAKEFLAGS= /usr/bin/make
rm -f verifyspec.o
rm -f *~ core *.core
/opt/poky/2.0/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-g++ -c -pipe -march=armv7-a -mfpu=neon -DLINUX=1 -DEGL_API_FB=1 -mfloat-abi=hard --sysroot=/dev/sdd -O2 -std=gnu++11 -Wall -W -fPIC -I. -I/home/qt/Descargas/qt5/qtbase/mkspecs/devices/linux-imx6-g++ -o verifyspec.o verifyspec.cpp
cc1plus: error: /dev/sdd/usr/include/c++/5.2.0: Not a directory
cc1plus: error: /dev/sdd/usr/include/c++/5.2.0/arm-poky-linux-gnueabi: Not a directory
cc1plus: error: /dev/sdd/usr/include/c++/5.2.0/backward: Not a directory
cc1plus: error: /dev/sdd/usr/lib/gcc/arm-poky-linux-gnueabi/5.2.0/include: Not a directory
cc1plus: error: /dev/sdd/usr/local/include: Not a directory
cc1plus: error: /dev/sdd/usr/include: Not a directory
Makefile:1006: fallo en las instrucciones para el objetivo 'verifyspec.o'
make: *** [verifyspec.o] Error 1I have that install more packges??
Regards
-
/dev/sdd
? Highly unlikely since it represent a drive on your system not even a partition but the whole physical drive.You need to pass the folder where you copied your device file system.
-
wrote on 24 Mar 2017, 18:15 last edited by Alexander-9
@SGaist @jsulm I already add the sysroot ./configure -release -opengl es2 -device linux-imx6-g++ -device-option CROSS_COMPILE=/opt/poky/2.0/sysroots/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi- -sysroot /media/qt/rootfs/ -prefix /usr/local/qt5, the sysroot contain the folders: bin, build, boot, etc, is correct??
Generates me this error of compilation: Config.log.
-
Did you do it from a clean state ?
-
wrote on 24 Mar 2017, 21:51 last edited by Alexander-9
@SGaist I have executed the command make clean, is correct or i have run other command??
-
Well, the best thing to do is an out of source build, so if something goes wrong you just nuke the folder and start anew. This has also the advantage to leave the sources untouched.
-
wrote on 24 Mar 2017, 22:18 last edited by
Because also delete of folder qt-everywhere-opensource-src-5.8.0 and again extract qt-everywhere-opensource-src-5.8.0.zip for run the ./configure
12/25