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.

Linux/AM5728: Qt Creator issue

Part Number: AM5728


Tool/software: Linux

Hello:
       I   compiled AM5728 platform's engineering using Qtcreator in the Ubuntu14.04 system, and the compiling error:

/home/linux/AM5728/linux-devkit/sysroots/armv7ahf-neon-linux-gnueabi/usr/include/gnu/stubs.h:7: error: gnu/stubs-soft.h: No such file or directory
# include <gnu/stubs-soft.h>
^

        Looking forward to your professional reply, thank you!


        The compile environment does not be checked out errors, and here is my installation environment:

1.Installed TI SDK   ti-processor-sdk-linux-rt-am57xx-evm-03.03.00.04-Linux-x86-Install.bin  to path:/home/linux/AM5728;

   Installed cross compile file to path:/home/linux/gcc-linaro-5.3-2016.02-x86_64_arm-linux-gnueabihf;

   Installed qt-creator-opensource-linux-x86_64-4.1.0.run to path: /home/linux/qtcreator-4.1.0.

2.Configuring Qt Creator

*Using TI SDK environment to enter Qt:

root@ubuntu:/home/linux# source /home/linux/AM5728/linux-devkit/environment-setup
[linux-devkit]:/home/linux> cd /home/linux/qtcreator-4.1.0/bin/
[linux-devkit]:/home/linux/qtcreator-4.1.0/bin> ./qtcreator

*Click Tool->Options->Build&Run->Compilers->Add->GCC:

compiler path:  /home/linux/AM5728/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/arm-linux-gnueabihf-g++;

*Click Tool->Options->Build&Run->Qt Versions->Add:

qmake location: /home/linux/AM5728/linux-devkit/sysroots/x86_64-arago-linux/usr/bin/qt5/qmake;

*Click Tool->Options->Build&Run->Debuggers->Add:

name: AM5728-Debugger

Path: /home/linux/gcc-linaro-5.3-2016.02-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-gdb

*Click Tool->Options->Build&Run->Kits->Add:

name:AM5728

Device type: Generic Linux Device

Compiler:GCC

Debugger:AM5728-Debugger

Qt version: Qt 5.6.2(qt5)

        Once again, Looking forward to your professional reply, thank you!