How to determine the Way(LinuxFB/XCB/..) when build the QT source code



  • Hi there,
    I'm trying to build the QT5.9.6 for the embedded linux platform.
    After built, I copy the lib and application file to the embedded linux, but the application could not be executed on the embedded platform.
    Is there any way to check the embedded linux platform display driver method?

    Regards,
    Simon


  • Lifetime Qt Champion

    Hi and welcome to devnet,

    Look at the summary of the configure call. You'll see all the backends that have been enabled.

    As for your device, what error did you get when starting your application ?
    Also, what backend are you interested in ?



  • Hi SGaist,
    Thank you. I'm new to QT.

    I'm trying to build QT, with command below:

    sudo ./configure -release -opensource -confirm-license -silent -nomake examples -nomake tools -no-opengl -no-dbus -no-xcb -qt-zlib -device linux-sam-neon-g++ -device-option CROSS_COMPILE=/home/simon/Workspace/Boards/smarc-imx7d/gcc-linaro-5.3.1/bin/arm-linux-gnueabihf- -sysroot /home/simon/Workspace/Boards/smarc-imx7d/ROOTFS -prefix /opt/Qt5.9.6
    

    It comes the errors:

    Running configuration tests...
    Checking for valid makespec... Note: Also available for Linux: linux-clang linux-icc
    
    ERROR: Cannot compile a minimal program. The toolchain or QMakeSpec is broken.
    
    Check config.log for details.
    

    Attached the config.log, How can i do for this?

    Regards,
    Simon[0_1531118637270_config.log](Uploading 100%)


  • Moderators

    @Simon.Chen.VIP Add -v parameter to your configure call and see what exactly is happening.



  • @jsulm

    Here is the outcome:

    > /home/simon/Workspace/Boards/smarc-imx7d/gcc-linaro-5.3.1/bin/arm-linux-gnueabihf-g++ -c -pipe -march=armv7-a -mfpu=neon -DLINUX=1 -mfloat-abi=hard --sysroot=/home/simon/Workspace/Boards/smarc-imx7d/ROOTFS -O2 -w -fPIC  -I/home/simon/Qt/5.9.6/Src/qtbase/config.tests/verifyspec -I. -I/home/simon/Qt/5.9.6/Src/qtbase/mkspecs/devices/linux-sam-neon-g++ -o verifyspec.o /home/simon/Qt/5.9.6/Src/qtbase/config.tests/verifyspec/verifyspec.cpp
    > /home/simon/Workspace/Boards/smarc-imx7d/gcc-linaro-5.3.1/bin/arm-linux-gnueabihf-g++ -mfloat-abi=hard --sysroot=/home/simon/Workspace/Boards/smarc-imx7d/ROOTFS -Wl,-O1 -o verifyspec verifyspec.o    
    > /home/simon/Workspace/Boards/smarc-imx7d/gcc-linaro-5.3.1/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/bin/ld: cannot find crt1.o: No such file or directory
    > /home/simon/Workspace/Boards/smarc-imx7d/gcc-linaro-5.3.1/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/bin/ld: cannot find crti.o: No such file or directory
    > /home/simon/Workspace/Boards/smarc-imx7d/gcc-linaro-5.3.1/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/bin/ld: cannot find -lm
    > collect2: error: ld returned 1 exit status
    > Makefile:66: recipe for target 'verifyspec' failed
    > make: *** [verifyspec] Error 1
    Note: Also available for Linux: linux-clang linux-icc
    
    ERROR: Cannot compile a minimal program. The toolchain or QMakeSpec is broken.
    

  • Lifetime Qt Champion

    What compiler was used to build your sysroot ?


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.