Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-68163

x86_64-pokysdk-linux/environment-setup.d/qt5.sh issues in b2qt SDK

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Not Evaluated
    • 5.11.0
    • 5.10.1
    • Device Creation
    • None
    • Sourcing  /opt/sdk/environment-setup-aarch64-poky-linux from a jenkins job

    Description

      Today I started adding jobs to jenkins that build software components using the cross compilation toolchain from a baked B2Qt SDK for TX2.

      At the beginning of the script I source . /opt/sdk/environment-setup-aarch64-poky-linux as I should.

      Sourcing this file from PC terminal only only shows warnings. But jenkins check every shell instructions return value to detect is the build is successful.

       

      export OE_QMAKE_CC=$CC
      export OE_QMAKE_CXX=$CXX
      export OE_QMAKE_LINK=$CXX

       

      should be changed to 

       

      export OE_QMAKE_CC="$CC"
      export OE_QMAKE_CXX="$CXX"
      export OE_QMAKE_LINK="$CXX"
      

      otherwise build fail with error:

       
      export OE_QMAKE_CC=aarch64-poky-linux-gcc --sysroot=/opt/sdk/sysroots/aarch64-poky-linux
      /tmp/jenkins6449859542230643733.sh: 5: export: --sysroot: bad variable name
      Also when executing that script these warnings show up:

       

      ...
      + qmake -query QT_INSTALL_LIBS Empty filename passed to function
      ...
      + qmake -query QT_INSTALL_HEADERS Empty filename passed to function
      ...
      + qmake -query QT_INSTALL_LIBS Empty filename passed to function
      ...
      + qmake -query QT_INSTALL_LIBS Empty filename passed to function
      ...
      

      It turns out that QT_INSTALL_LIBS and QT_INSTALL_HEADERS are not defined. I'm not aware of the impact of these warning at this stage

       

      Attachments

        For Gerrit Dashboard: QTBUG-68163
        # Subject Branch Project Status CR V

        Activity

          People

            sapiippo Samuli Piippo
            damienlefevre Damien LEFEVRE
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes