Skip to content
  • 0 Votes
    1 Posts
    706 Views
    No one has replied
  • 0 Votes
    2 Posts
    1k Views
    SGaistS

    Hi,

    Not really a Qt question, you should rather check on the IMX/Linux distribution you're using to see what is happening

  • 0 Votes
    10 Posts
    24k Views
    K

    oops.. Sorry for the name.
    Actually I am developing my application for Ubuntu and right now no plan to port on other platform. But If I face any problem I will post here.. :D
    Thanks tomasz3dk :)

  • 0 Votes
    2 Posts
    2k Views
    S

    I have same problem with GST, but in 0,1 version.
    GST launch working, but Qt cannot find m_videoSink, even modify qgstreamervideowindow.cpp doesn't work.

  • 0 Votes
    5 Posts
    6k Views
    S

    Hi

    May I ask how you got this to build?

    I am trying to compile Qt with the following configuration (for Raspberry Pi):

    ./configure --prefix=/usr -release -opensource -confirm-license -c++11 -no-largefile -no-qml-debug -system-zlib \ -no-journald -system-libpng -system-freetype -system-libjpeg -system-sqlite -openssl -no-pulseaudio -alsa \ -no-sql-db2 -no-sql-ibase -no-sql-mysql -no-sql-oci -no-sql-odbc -no-sql-psql -no-sql-sqlite2 -no-sql-tds -nomake examples -reduce-exports \ -no-directfb -no-linuxfb -eglfs -no-xcb -device linux-rasp-pi-g++ -device-option CROSS_COMPILE=/usr/bin/ -sysroot /

    Here is my patch:

    diff --git a/qtwebengine/tools/qmake/mkspecs/features/functions.prf b/qtwebengine/tools/qmake/mkspecs/features/functions.prf index ef0320d..5abaecc 100644 --- a/qtwebengine/tools/qmake/mkspecs/features/functions.prf +++ b/qtwebengine/tools/qmake/mkspecs/features/functions.prf @@ -12,13 +12,9 @@ defineTest(isPlatformSupported) { return(false) } - linux-g++*:!isGCCVersionSupported(): return(false) - !isPythonVersionSupported(): return(false) - linux-g++*|win32-msvc2013|macx-clang: return(true) boot2qt: return(true) - skipBuild("Qt WebEngine can currently only be built for Linux (GCC), Windows (MSVC 2013), OS X (XCode 5.1+) or Qt for Device Creation.") - return(false) + return(true) } defineTest(isPythonVersionSupported) { -- 2.1.0

    And it succeeds, but I don't get a message about WebEngine being an unsupported platform. It simply does not build that module. I tried to follow this reference here, but had no luck either: https://forum.qt.io/topic/48223/webengine-raspberry-pi/2

    I am building native, not cross, on Debian Jessie.

    Thanks in advance,

    Sam

  • 0 Votes
    1 Posts
    2k Views
    No one has replied
  • 0 Votes
    2 Posts
    1k Views
    SGaistS

    Hi,

    It depends partly on what you use on your board, do you have a X server running ?

  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • 0 Votes
    5 Posts
    3k Views
    K

    I am working on Nitrogen6 Max Board using Ubuntu Trusty for i.MX6 boards img (light weight desktop environment).
    I have downloaded img file from timesys for direct use http://boundarydevices.com/trusty-ubuntu-mx6/.

  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • 0 Votes
    4 Posts
    11k Views
    B

    @Phill-ONeill said:

    -prefix $usr -xplatform linux-arm-g++-cross -release -opensource
    -no-largefile -no-qml-debug -system-zlib -no-gif -qt-libpng -qt-libjpeg -qt-freetype
    -no-xcb -no-xkbcommon -no-pulseaudio -no-alsa -no-gtkstyle -nomake "examples tests"
    -no-rpath -no-nis -no-cups -no-fontconfig -no-kms -no-pch -no-directfb -no-sql-sqlite -no-xcb
    -eglfs -mtdev -opengl -tslib -skip qtactiveqt -skip qtconnectivity -skip qtdoc -skip qtenginio
    -skip qtgraphicaleffects -skip qtimageformats -skip qtlocation -skip qtmultimedia -skip qtsensors
    -skip qtserialport -skip qtsvg -v

    This gives me the following error: linux-arm-g++-cross: unknown argument

    @mokat said:

    sudo ./configure -opensource -confirm-license -developer-build -nomake examples -nomake tests -skip qtwebkit -device imx6 -prefix /usr/local/

    Running this command gives me this:

    Creating qmake...
    .Done.
    Running configuration tests...
    Failed to process makespec for platform 'devices/linux-imx6-g++'

    Which gives me:

    Creating qmake...
    make: Nothing to be done for `first'.
    Running configuration tests...
    Failed to process makespec for platform 'devices/linux-imx6-g++'
    Project ERROR: CROSS_COMPILE needs to be set via -device-option CROSS_COMPILE=<path>
    Could not read qmake configuration file /home/bob/qt5/qtbase/mkspecs/devices/linux-imx6-g++/qmake.conf.
    Error processing project file: /dev/null

    So I add -device-option with: -device-option CROSS_COMPILE=/home/bob/Downloads/gcc-linaro-arm-linux-gnueabi/bin/arm-linux-gnueabi-

    sudo ./configure -v -opensource -confirm-license -developer-build -nomake examples -nomake tests -skip qtwebkit -device imx6 -prefix /usr/local/ -device-option CROSS_COMPILE=/home/bob/Downloads/gcc-linaro-arm-linux-gnueabi/bin/arm-linux-gnueabi-

    Which gives me the following Warnings:

    Creating qmake...
    .Done.
    Running configuration tests...
    Warning: Disabling pkg-config since PKG_CONFIG_LIBDIR is not set.
    Warning: Disabling pkg-config since PKG_CONFIG_SYSROOT_DIR is not set.
    Could not determine the target architecture!
    Turn on verbose messaging (-v) to see the final report.
    WARNING: Unable to find file .device.vars
    No QPA platform plugin enabled!
    If you really want to build without a QPA platform plugin you must pass
    -no-qpa-platform-guard to configure. Doing this will
    produce a Qt that can not run GUI applications.
    The dependencies needed for xcb to build are listed in
    src/plugins/platforms/xcb/README

    If I check this readme it tells me the dependencies I need and suggest using -qt-xcb to reduce dependencies. I have the dependencies so I add -qt-xcb to the end of my command

    sudo ./configure -v -opensource -confirm-license -developer-build -nomake examples -nomake tests -skip qtwebkit -device imx6 -prefix /usr/local/ -device-option CROSS_COMPILE=/home/bob/Downloads/gcc-linaro-arm-linux-gnueabi/bin/arm-linux-gnueabi- -qt-xcb

    This spew this pile of errors: http://pastebin.com/uh9EYs1y

    Would re-installing Ubuntu or something work? I'm really at the end of my options. Everywhere people seem to be able to run these ./configure commands with some options easily. For me it just spews lines of errors and stuff. As you can see above trying to get the command you use to work results in work followed by not working anywa

  • 0 Votes
    9 Posts
    6k Views
    J

    The static build is failing inside of Yocto. All I have done to get this to fail is to change -shared to -static inside of qtbase.bb and then $ bitbake meta-toolchain-qt5. Building Qt dynamically will successfully create the SDK, but not statically.

    I have found someone with the exact same problem here. The plugin lib directory path is incorrect and has the cross compile prefix omitted causing problems finding the necessary libraries.

    I've posted my build environment and error output here.

  • 0 Votes
    2 Posts
    1k Views
    p3c0P

    Hi @atessadri,

    I would like to know how to understand when the animation embedded in the transition is really finished.
    Is there any signal to catch ?

    Yes there is. Transition has running property so you can use the onRunningChanged signal handler inside it. Eg:

    Transition { ... onRunningChanged: if(!running) console.log("Stopped") }

    Sorry I don't have answers to your other questions.

  • 0 Votes
    3 Posts
    2k Views
    A

    This maybe due to the fact that our IMX6 board does not have the plugins/mediaservice particularly the libgstmediaplayer.so. Does anyone know how to create this library? And which directory in the IMX6 do I put this if I have successfully cross compiled it?

  • 0 Votes
    1 Posts
    2k Views
    No one has replied
  • 0 Votes
    1 Posts
    827 Views
    No one has replied
  • 0 Votes
    5 Posts
    4k Views
    A

    It depends if it's a Qt Quick application or not. If you are using widgets or doing your own custom OpenGL rendering then there will be no problem. The issue with Qt Quick is that it has its own animation system which gets driven by the default 16.66 ms on platforms where it fails to query the real refresh rate from the system. Run with QSG_INFO=1 to verify the actual value that is in use. (NB Qt 5.5 has some improvements in this area - https://bugreports.qt.io/browse/QTBUG-44971 - so it is now able to retrive the correct refresh rate on embedded platforms too)