Cross compilation with X11
-
Did you do a full copy of the sysroot over to your desktop ?
On a side note, unless you're locked to that version, at least use the latest of the Qt 4 series which is 4.8.7. Even better if you migrate to Qr 5.
-
Did you do a full copy of the sysroot over to your desktop ?
On a side note, unless you're locked to that version, at least use the latest of the Qt 4 series which is 4.8.7. Even better if you migrate to Qr 5.
-
Yes. I have copied all the files. May I know how to configured sysroot on local desktop ? Could please tell me the steps.
-
@thanga "Could please tell me the steps" - we already did.
Does this file exist on your target device?
Did you copy recursively (I mean: including subdirectories)? -
What do you mean by "without adding target device on Qt Creator" ?
-
We are mounting and adding Beagleboard device (on Qt Creator) for compiling Qt application.
Add device on Qt Creator:
Qt Creator -> Tools -> Devices -> Add DeviceMounting Device (Beagleboard):
/media/SSHFS_X11/Is it possible to compile Qt application without Beagleboard device ?
-
If you don't want to mount the device root filesystem while developing then you have to provide a sysroot to work with.
-
If you don't want to mount the device root filesystem while developing then you have to provide a sysroot to work with.
@SGaist
Hi,
thanks, I got confused on providing "sysroot".
I am looking for a way to cross compile Qt application for beaglebone without adding and mounting to Host PC either through SCP or as file system. Because to update and rebuild the Qt application each time its leading to mount the device to PC host.
Is there any other way to do? or it is not possible !!! -
If you don't want to mount your device while developing for it then you have to copy its root filesystem on your computer and use that copy as sysroot when cross-compiling Qt. You will also have to keep that copy up to date if you need to add a new dependency for your application.
-
If you don't want to mount your device while developing for it then you have to copy its root filesystem on your computer and use that copy as sysroot when cross-compiling Qt. You will also have to keep that copy up to date if you need to add a new dependency for your application.
@SGaist
Thanks! How to compile Qt application without device ?We are adding device on Qt Creator, is it possible to compile the application without device ? Please check the below link for your reference.
Qt Creator link: http://www.qnx.com/developers/docs/660/topic/com.qnx.doc.qt/images/qt_creator_add_device_button.png
http://docs.toradex.com/101754-01-qtcreator-linux-devices.png -
I already wrote it several times: if you want to cross-compile without any device connected, then copy the root filesystem of your device on your desktop machine and cross-compile Qt using it.
One thing to be clear: if you want to run your cross-compiled application, then you need your device accessible to run said application.
Out of curiosity, why do you want that much to cross-compile an application without any device connected to confirm it runs properly ?
-
I already wrote it several times: if you want to cross-compile without any device connected, then copy the root filesystem of your device on your desktop machine and cross-compile Qt using it.
One thing to be clear: if you want to run your cross-compiled application, then you need your device accessible to run said application.
Out of curiosity, why do you want that much to cross-compile an application without any device connected to confirm it runs properly ?
@SGaist
One of our device is not on network and cannot be mounted. We would like to cross compile the code using QTCreator and copy the executable manually on the target using a SD Card. Let us know if this is possible.
If yes, then what should be the hostname and credentials in QTCreator Add Device screen? -
Since your device is out of reach, it doesn't make sense to put anything there. Just don't add any device. Build your executable and then copy it on your SD card.
-
Since your device is out of reach, it doesn't make sense to put anything there. Just don't add any device. Build your executable and then copy it on your SD card.
@SGaist
Thanks! I have tried it in the same method. I am getting following error. Could please check it,usr/local/linaro/bin/../lib/gcc/arm-linux-gnueabihf/4.7.3/../../../../arm-linux-gnueabihf/bin/ld: note: 'clock_gettime@@GLIBC_2.4' is defined in DSO /media/SSHFS_X11//lib/arm-linux-gnueabihf/librt.so.1 so try adding it to the linker command line
/media/SSHFS_X11//lib/arm-linux-gnueabihf/librt.so.1: could not read symbols: Invalid operation -
Is that were your device root filesystem has been copied ?
-
@SGaist
QTCreator has an option sysroot wherein it expects the sysroot of the target board. Should the path be the mounted path on actual board ?If we have limited set of boards, can we create the ISO image of the target device, copy it on SD Card and then mount it and use this path as Sysroot path. Can we use this to create multiple development systems(environment) which are not dependent on target board.
-
You can copy the content of the root filesystem of your device only our desktop computer and use that as sysroot. Just keep in mind that you'll have to keep it up to date yourself.
-
You can copy the content of the root filesystem of your device only our desktop computer and use that as sysroot. Just keep in mind that you'll have to keep it up to date yourself.
@SGaist
We have copied the contents of the root filesystem and tried to compile it. We are getting an error as mentioned below. Please note that we are mounting this on a i386 32 bit machine. The target board is arm-linux../NewQTApp/release/build/arm926/libftd2xx.a(ftd2xx.o): In function `InitCheckDevice':
ftd2xx.c:(.text+0x2d0): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/local/linaro/bin/../lib/gcc/arm-linux-gnueabihf/4.7.3/../../../../arm-linux-gnueabihf/bin/ld: ../NewQTApp/release/build/arm926/libftd2xx.a(linux_usbfs.o): undefined reference to symbol 'clock_gettime@@GLIBC_2.4'
/usr/local/linaro/bin/../lib/gcc/arm-linux-gnueabihf/4.7.3/../../../../arm-linux-gnueabihf/bin/ld: note: 'clock_gettime@@GLIBC_2.4' is defined in DSO /media/SSHFS_X11//lib/arm-linux-gnueabihf/librt.so.1 so try adding it to the linker command line
/media/SSHFS_X11//lib/arm-linux-gnueabihf/librt.so.1: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
make: *** [NewQTApp] Error 1
20:15:03: The process "/usr/bin/make" exited with code 2.
Error while building/deploying project NewQTApp (kit: Linaro) -
Looks like there's a mismatch between the version of gcc used to build your application and the one used for the sysroot.
-
Looks like there's a mismatch between the version of gcc used to build your application and the one used for the sysroot.
