Qmake creating makefile with wrong libraries/include

  • Hello,

    I try to compile a qt project for embedded system.
    But when running qmake, I get wrong include directories and wrong libraries.
    If I set them manually in makefile, it compiles OK.

    Does anyone knows what should be done in order that qmake will create the Makefile with the correct include/libs ?

    Thank you,

  • Lifetime Qt Champion


    Are you running the qmake version that corresponds to the Qt framework built for your embedded system ?

  • Hi,

    Yes, I do.
    But I probably missed something in the process.
    This is the contents of qmake.conf, where/how should the lib and include directories should be configured ? Thx, Ran

    linux-TIarmv7-g++$ cat qmake.conf

    qmake configuration for building with arm-linux-g++


    modifications to g++.conf

    QMAKE_CFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp
    QMAKE_CXXFLAGS_RELEASE = -O3 -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=softfp

    QMAKE_CC = arm-none-linux-gnueabi-gcc
    QMAKE_CXX = arm-none-linux-gnueabi-g++
    QMAKE_LINK = arm-none-linux-gnueabi-g++
    QMAKE_LINK_SHLIB = arm-none-linux-gnueabi-g++

    modifications to linux.conf

    QMAKE_AR = arm-none-linux-gnueabi-ar cqs
    QMAKE_OBJCOPY = arm-none-linux-gnueabi-objcopy
    QMAKE_STRIP = arm-none-linux-gnueabi-strip


  • Hi,

    I also get a worning when executing qmake:
    ubuntu@ubuntu-laptop:/media/sdd/gui_app/sender$ /media/sdb/qt/qt-everywhere-opensource-src-4.8.1/bin/qmake -spec /media/sdb/qt/qt-everywhere-opensource-src-4.8.1/mkspecs/qws/linux-TIarmv7-g++
    Project WARNING: Your mkspec is including 'common/g++.conf', but the mkspecs have been refactored
    To fix this include 'common/gcc-base-.conf and 'common/g++-.conf' instead

    Do you think it might indicate why the include/libraries are wrong in makefile ?


  • Lifetime Qt Champion

    I would indeed correct that first.

    Also, unless you're locked to that version you should consider updating to the latest version of Qt

Log in to reply

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.