Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

[Solved] Developing with Ubuntu Qt Creator ToolChain for Angstrom Beaglebone Black



  • I posted this in another Qt forum and there isn't any response so maybe it is just out of context.

    I am trying to develop applications for the beaglebone black angstrom linux distribution.

    I have downloaded the toolchain:

    angstrom-2011-03-x8x_64-linux-arm7a-linux-gnueabi-toolchain-qte-4.6.3.tar.bz2

    I have extracted it and run the environment-setup script so when I create a shell all of the environment variables are present.

    for example:

    OE_QMAKE_AR=arm-angstrom-linux-gnueabi-ar
    ...

    I downloaded and installed

    qt-opensource-linux-x64-1.5.0-1-online.run

    I created a new kit:
    Name: arm-angstrom
    Device Type: Generic Linux Type // not too many choices here
    Device: Generic Linux Device (default for Generic Linux)
    Sysroot: who knows
    Compiler GCC
    Debugger: System GDB /usr/bin/gdb // link to angstrom debugger
    Qt version: Qt 5.2.1 GCC 64 bit
    Qt mkspwc:/usr/local/angstrom/arm-angstrom-linux-gnueabi/usr/share/qtopia/mkspec/linux-g++
    The compiler
    Name: GCC
    Compiler path: /usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-9++
    Platform codegen: who knows
    Platform linker: Who knows
    ABI: Custom arm linux generic elf 64bit
    Devices
    Name Generic Linux Device
    Machine Type: Physical Device
    Hostname: 192.168.7.1 ssh port: 22
    Tested and verified
    The project run key selector still thinks its a local even when the kit points to the remote device?

    I was under the impression that Qt would read the environment variables setup by the environment-setup and know what to do :-) What am I doing wrong?



  • Hello I'm not sure if I can help you. What are you trying to do? Are you try to run the remote debugger? Please give me a little bit more information.


Log in to reply