Uploaded image for project: 'Qt Creator'
  1. Qt Creator
  2. QTCREATORBUG-19775

Configuring project using BootToQt Kit based on dev branch of Qt results in no files deployed/run configuration executable

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P2: Important
    • Resolution: Invalid
    • Affects Version/s: Qt Creator 4.5.0
    • Fix Version/s: None
    • Component/s: Boot2Qt Support
    • Labels:
      None

      Description

      Steps I took before encountering this:

      1. Checked out this declarative change: https://codereview.qt-project.org/#/c/219182/
      2. Built Qt 5 for Nitrogen 6 with this script:
        #! /bin/bash
        
        qtSdkDir=/home/mitch/dev/qt-unified
        qtSourceDir=/home/mitch/dev/qt5-dev
        qtBuildDir=/home/mitch/dev/qt5-dev-n6-debug
        qtHostPrefix=$qtBuildDir/hostbin
        devicePrefix=/usr/local/qt5-dev
        deviceName=nitrogen6x
        deviceMkspec=linux-imx6-g++
        sysrootDir=$qtSdkDir/5.9.3/Boot2Qt/$deviceName/toolchain/sysroots
        armSysrootDir=$sysrootDir/cortexa9hf-neon-poky-linux-gnueabi
        crossCompile=$sysrootDir/x86_64-pokysdk-linux/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-
        
        set -e
        
        echo "qtSdkDir=$qtSdkDir"
        echo "qtSourceDir=$qtSourceDir"
        echo "qtBuildDir=$qtBuildDir"
        echo "devicePrefix=$devicePrefix"
        echo "sysrootDir=$sysrootDir"
        echo "armSysrootDir=$armSysrootDir"
        echo "hostprefix=$qtHostPrefix"
        
        echo "\n"
        
        echo "About to remove $qtBuildDir"
        rm -fr $qtBuildDir
        
        echo "About to mkdir $qtBuildDir"
        mkdir $qtBuildDir
        
        echo "About to cd into build dir $qtBuildDir"
        cd $qtBuildDir
        
        echo "About to configure Qt build"
        
        # -device-option DISTRO_OPTS=boot2qt is necessary for https://bugreports.qt.io/browse/QTBUG-61962
        $qtSourceDir/configure -v -commercial -confirm-license -debug -prefix $devicePrefix -hostprefix $qtHostPrefix -extprefix $armSysrootDir/$devicePrefix -device $deviceMkspec -device-option CROSS_COMPILE=$crossCompile -sysroot $armSysrootDir -nomake tests -nomake examples -no-pch -opengl es2 -device-option DISTRO_OPTS=boot2qt
        
        echo "About to run make"
        make -j 8
        
        echo "About to run make install"
        make install
        
      3. Added this Qt version to Creator (/home/mitch/dev/qt5-dev-n6-debug/hostbin/bin/qmake).
      4. Added kit using this Qt version to Creator (cloned Boundary Devices i.MX6 kit that the SDK adds). There were no warnings.
      5. Pushed Qt build to device:
        rsync -avz --exclude=doc --exclude=include --exclude=*.debug /home/mitch/dev/qt-unified/5.9.3/Boot2Qt/nitrogen6x/toolchain/sysroots/cortexa9hf-neon-poky-linux-gnueabi/usr/local/qt5-dev root@1.2.3.4:/usr/local/
        
      6. Opened tests/manual/tableview/abstracttablemodel/abstracttablemodel.pro from the change mentioned above in Creator, configured it using the newly added qt5-dev-n6-debug kit. Creator asks me to specify a custom executable. Upon inspecting the Run configuration in the Projects mode, I can see that no files are deployed, and the only run configuration is "Custom executable". Interestingly, if I click on "Add" next to that configuration, one of the options is "tableview_abstracttablemodel (on Boot2Qt device)", suggesting that it is somewhat aware of it, but not enough to set it up for me automatically. Adding that run configuration doesn't help, because it still doesn't deploy the application's files.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            kari.oikarinen Kari Oikarinen
            Reporter:
            mitch_curtis Mitch Curtis
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes