• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 742 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Compiling Qt Applications

abraxas
Prodigy 230 points

Hello,

I started creating a Qt application, which i can debug and start in my IDE.

Qt is also working on my OMAP3EVM (unfortunatly without touchscreen support, although ts_test and test_calibrate work.. but thats another problem...), e.g. i can run the demos.

But I'm stuck on how i can compile my project for the ARM processor. I have set the PATH to my qmake file and set QMAKESPEC=g++.

But for "qmake -o test" i get a "could not find mkspecs for your QMAKESPEC(g++) after trying /opt/qt//mkspecs"

This seems like a very basic error, but i could not find any hints on the web.

  • 0
    TI__Mastermind 44306 points

    So far it is not clear what kind of environment you have. We can only help if we understand that as there are so many options.

    Did you configure your own Qt port or use some DVSDK as base (if yes, which version)? What Qt mkspec did you use then? Are you on X or just using Qt QWS system? Are you cross-compiling or native on the target?

    In general you should use the same mkspec that has been used to build the ARM Qt libs.  Obviously this needs to exist in your Qt environment and for the ARM build it should define the correct compiler names.

    Regards.

  • 0 in reply to Frank Walzer
    Prodigy 230 points

    well ehm ok, I try to give more information. i hobe this is what you need. I'm at the moment at my home pc, so i cant look up everyhting in detail.

    On my board, theres the recent nfs_dvsdk version. As host i  use fedora13, on which i built my Qt.

    So far, i did cross.compile  to the target (the nfs_dvsk for linux).

    I used the Code Sourcery compiler for building my Qt

  • 0 in reply to abraxas
    Prodigy 230 points

    I really shouldn't work after 5PM ;)

    Simple solution:

    i set

    export QMAKESPEC=<where my qmake.conf is>

    then

    (if there's no .pro file type this first in the directory where the cpp and so on are: qmake -project)

    qmake -o Makefile

    make

     

  • 0 in reply to Frank Walzer
    Intellectual 850 points

    To all Qt experts,

    In order to understand how Qt works with the DVSDK 4.x for the DM365, my goal is to make simple modifications to the qtInterface app.  As a starting starting point, I've tried to rebuild the qtInterface app by following the instructions for building Qt apps found at the bottom of page 16/top of page 17 of the SDG supplied with DVSDK 4.01 then run it in conjunction with one of the demo apps.  Starting with a clean qtInterface directory, here are the command line elements I have executed:

    1. [linux-devkit]:~/ti-dvsdk_dm365-evm_4_01_00_09/dvsdk-demos_4_00_00_21/qtInterface> qmake -project

    2. [linux-devkit]:~/ti-dvsdk_dm365-evm_4_01_00_09/dvsdk-demos_4_00_00_21/qtInterface> qmake

    3. [linux-devkit]:~/ti-dvsdk_dm365-evm_4_01_00_09/dvsdk-demos_4_00_00_21/qtInterface> make PLATFORM=dm365

    4. [linux-devkit]:~/ti-dvsdk_dm365-evm_4_01_00_09/dvsdk-demos_4_00_00_21/qtInterface> sudo cp qtInterface ${HOME}/targetfs/usr/share/ti/dvsdk-demos

    5. root@dm365-evm:/usr/share/ti/dvsdk-demos# /etc/init.d/loadmodule-rc restart

    6. root@dm365-evm:/usr/share/ti/dvsdk-demos# ./encode -v Avatar.264 -a Avatar.aac -o | tee log.txt

    The qtInterface app returns the following: Failed to open /sys/devices/platform/omapdss/overlay0/enabled for writing

    This makes no sense at all!  Why the reference to "omapdss" when my platform is the DM365?  What am I missing?  

    So far my app development has gone relatively smoothly but this one has me puzzled - any help will be greatly appreciated.

    BTW: my development platform is the EVMDM365.

    Thanks,

    -Chuck

  • 0 in reply to Chuck@Cimarron Systems
    Intellectual 850 points

    All,

    Regarding the "failure to build" the qtInterface application:

    I found the problem: the qtInterface application did not have the platform defined e.g., #define Platform_dm365 so "make" was building for the OMAP 3530 platform by default.

    Suggestion: the Qt application sections of the SDG should be updated to alert developers of the need to define the platform before attempting to built the qtInterface app and a similar note should be added to the appropriate Qt Wiki page.

    -Chuck