Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. QT5.9.6 build in ARM EC-A3399C
Forum Updated to NodeBB v4.3 + New Features

QT5.9.6 build in ARM EC-A3399C

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
7 Posts 2 Posters 908 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    goldLovemoon
    wrote on last edited by
    #1

    Here is my qmake.conf
    MAKEFILE_GENERATOR = UNIX
    CONFIG += incremental
    QMAKE_INCREMENTAL_STYLE = sublib

    QMAKE_INCDIR = /usr/include
    /usr/include/aarch64-linux-gnu
    QMAKE_LIBDIR = /lib
    /usr/lib
    /lib/aarch64--linux-gnu

    QMAKE_INCDIR_OPENGL[_ES2] += /usr/include/GLES2
    /usr/include/EGL
    /usr/include/GLES3
    /usr/include/KHR

    QMAKE_LIBDIR_OPENGL[_ES2] = /usr/lib/aarch64-linux-gnu

    QMAKE_LIBS_OPENGL_ES2 += -lGLESv2 -lEGL

    include(../common/linux.conf)
    include(../common/gcc-base-unix.conf)
    include(../common/g++-unix.conf)

    modifications to g++.conf

    QMAKE_CC = aarch64-linux-gnu-gcc
    QMAKE_CXX = aarch64-linux-gnu-g++
    QMAKE_LINK = aarch64-linux-gnu-g++
    QMAKE_LINK_SHLIB = aarch64-linux-gnu-g++

    modifications to linux.conf

    QMAKE_AR = aarch64-linux-gnu-ar cqs
    QMAKE_OBJCOPY = aarch64-linux-gnu-objcopy
    QMAKE_NM = aarch64-linux-gnu-nm -P
    QMAKE_STRIP = aarch64-linux-gnu-strip

    #EGLFS_DEVICE_INTEGRATION = eglfs_brcm

    load(qt_config)

    My configure is
    ./configure -release -xplatform linux-arm-gnueabi-g++ -sysroot / -I/usr/include/c++/7 -no-opengl -opengl es2 -eglfs -linuxfb -prefix /opt/qt5.9.6-arm -opensource -confirm-license -make libs -no-pch -no-iconv -nomake tools -nomake examples -nomake tests -skip qtandroidextras -skip qtconnectivity -skip qtdatavis3d -skip qtdoc -skip qtgamepad -skip qtimageformats -skip qtlocation -skip qtmacextras -skip qtmultimedia -skip qtnetworkauth -skip qtpurchasing -skip qtsensors -skip qtserialbus -skip qtspeech -skip qtsvg -skip qttools -skip qtwebchannel -skip qtwebengine -skip qtwebsockets -skip qtwebview -skip qtwinextras -no-feature-iconv -no-feature-gestures -no-qml-debug

    when I configure qt source in arm, occurred an error:
    Note:Also available for linux:linux-clang linux-icc
    Note:Dropped compiler flags 'pthread' when detecting library 'glib'
    Note:Disabling X11 Accessibility Bridge: D-Bus or AT-SPI is missing
    Note:No wayland-egl support detected. Cross-toolkit compatibility disabled
    ERROR:Qt requires a compliant STL library

    jsulmJ 1 Reply Last reply
    0
    • G goldLovemoon

      Here is my qmake.conf
      MAKEFILE_GENERATOR = UNIX
      CONFIG += incremental
      QMAKE_INCREMENTAL_STYLE = sublib

      QMAKE_INCDIR = /usr/include
      /usr/include/aarch64-linux-gnu
      QMAKE_LIBDIR = /lib
      /usr/lib
      /lib/aarch64--linux-gnu

      QMAKE_INCDIR_OPENGL[_ES2] += /usr/include/GLES2
      /usr/include/EGL
      /usr/include/GLES3
      /usr/include/KHR

      QMAKE_LIBDIR_OPENGL[_ES2] = /usr/lib/aarch64-linux-gnu

      QMAKE_LIBS_OPENGL_ES2 += -lGLESv2 -lEGL

      include(../common/linux.conf)
      include(../common/gcc-base-unix.conf)
      include(../common/g++-unix.conf)

      modifications to g++.conf

      QMAKE_CC = aarch64-linux-gnu-gcc
      QMAKE_CXX = aarch64-linux-gnu-g++
      QMAKE_LINK = aarch64-linux-gnu-g++
      QMAKE_LINK_SHLIB = aarch64-linux-gnu-g++

      modifications to linux.conf

      QMAKE_AR = aarch64-linux-gnu-ar cqs
      QMAKE_OBJCOPY = aarch64-linux-gnu-objcopy
      QMAKE_NM = aarch64-linux-gnu-nm -P
      QMAKE_STRIP = aarch64-linux-gnu-strip

      #EGLFS_DEVICE_INTEGRATION = eglfs_brcm

      load(qt_config)

      My configure is
      ./configure -release -xplatform linux-arm-gnueabi-g++ -sysroot / -I/usr/include/c++/7 -no-opengl -opengl es2 -eglfs -linuxfb -prefix /opt/qt5.9.6-arm -opensource -confirm-license -make libs -no-pch -no-iconv -nomake tools -nomake examples -nomake tests -skip qtandroidextras -skip qtconnectivity -skip qtdatavis3d -skip qtdoc -skip qtgamepad -skip qtimageformats -skip qtlocation -skip qtmacextras -skip qtmultimedia -skip qtnetworkauth -skip qtpurchasing -skip qtsensors -skip qtserialbus -skip qtspeech -skip qtsvg -skip qttools -skip qtwebchannel -skip qtwebengine -skip qtwebsockets -skip qtwebview -skip qtwinextras -no-feature-iconv -no-feature-gestures -no-qml-debug

      when I configure qt source in arm, occurred an error:
      Note:Also available for linux:linux-clang linux-icc
      Note:Dropped compiler flags 'pthread' when detecting library 'glib'
      Note:Disabling X11 Accessibility Bridge: D-Bus or AT-SPI is missing
      Note:No wayland-egl support detected. Cross-toolkit compatibility disabled
      ERROR:Qt requires a compliant STL library

      jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote on last edited by
      #2

      @goldlovemoon said in QT5.9.6 build in ARM EC-A3399C:

      ERROR:Qt requires a compliant STL library

      What is the version of your cross compiler?
      Also, add -v parameter to configure call and see what exactly happens when configure tests for STL.

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      G 1 Reply Last reply
      0
      • jsulmJ jsulm

        @goldlovemoon said in QT5.9.6 build in ARM EC-A3399C:

        ERROR:Qt requires a compliant STL library

        What is the version of your cross compiler?
        Also, add -v parameter to configure call and see what exactly happens when configure tests for STL.

        G Offline
        G Offline
        goldLovemoon
        wrote on last edited by
        #3

        @jsulm gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz this is the compiler I used

        jsulmJ 1 Reply Last reply
        0
        • G goldLovemoon

          @jsulm gcc-linaro-7.2.1-2017.11-x86_64_aarch64-linux-gnu.tar.xz this is the compiler I used

          jsulmJ Offline
          jsulmJ Offline
          jsulm
          Lifetime Qt Champion
          wrote on last edited by
          #4

          @goldlovemoon "-sysroot /" - this doesn't look right. You can't use your host file system as sysroot for your device.

          https://forum.qt.io/topic/113070/qt-code-of-conduct

          G 1 Reply Last reply
          1
          • jsulmJ jsulm

            @goldlovemoon "-sysroot /" - this doesn't look right. You can't use your host file system as sysroot for your device.

            G Offline
            G Offline
            goldLovemoon
            wrote on last edited by
            #5

            @jsulm I compile qt resource in arm,so sysroot is the arm root

            1 Reply Last reply
            0
            • G Offline
              G Offline
              goldLovemoon
              wrote on last edited by
              #6

              @jsulm May I ask a question, why cross compiler Qt with opengl depends arm sysroot, why not build opengl in virtual machine, then transplant environment to arm

              jsulmJ 1 Reply Last reply
              0
              • G goldLovemoon

                @jsulm May I ask a question, why cross compiler Qt with opengl depends arm sysroot, why not build opengl in virtual machine, then transplant environment to arm

                jsulmJ Offline
                jsulmJ Offline
                jsulm
                Lifetime Qt Champion
                wrote on last edited by jsulm
                #7

                @goldlovemoon said in QT5.9.6 build in ARM EC-A3399C:

                why not build opengl in virtual machine, then transplant environment to arm

                I'm not sure I understand your question. When cross compiling for a different architecture you need a crosscompiler and sysroot for your device. A virtual machine will not help here.
                I guess your host machine is x86, right? That means, to build for ARM you need a compiler running on x86 but generating binaries for ARM. And you need sysroot containing the stuff from the file system of your device (libs, include files).

                https://forum.qt.io/topic/113070/qt-code-of-conduct

                1 Reply Last reply
                1

                • Login

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups
                • Search
                • Get Qt Extensions
                • Unsolved