qmake /bin/sh: OE_QMAKE_CXX: command not found?

[jsulm]

@kptt Can you show your .pro file? You're probably using these variables wrongly.

[kptt]

@jsulm This is my top level .pro file:

1 TEMPLATE = subdirs
2 SUBDIRS = \
3     lib \
4     examples
5 
6 !macx: { SUBDIRS += gpsd_plugin }
7 
8 #Some host installations have target dependencies installed in Qt root, not system root:
9 !linux-oe-g++ {
10     INCLUDEPATH += $$[QT_HOST_PREFIX]/usr/include
11     LIBS += -L$$[QT_HOST_PREFIX]/usr/lib
12 }
13 
14 examples.depends = lib

I have three other small .pro files that build different parts of the project.

I thought OE_QMAKE_CXX is supposed to point to the c++ cross compiler and OE_QMAKE_CXXFLAGS is supposed to contain all of the desired c++ compiler flags? Is it not? As far as I can tell, that's exactly what I'm doing.

[SGaist]

Hi and welcome to devnet,

Can you call arm-poky-linux-gnueabi-g++directly in your console ? If not then you should add the path to the folder containing it to the PATH environment variable.

[kptt]

Hi @SGaist,

Yes, I can invoke arm-poky-linx-gnueabi-g++ directly in my console (w/o a full path):

kevin at kp-workstation in ~
$ cd ~/sdk
kevin at kp-workstation in ~/sdk
$ ls
environment-setup-cortexa9hf-neon-poky-linux-gnueabi
relocate_sdk.py
relocate_sdk.sh
site-config-cortexa9hf-neon-poky-linux-gnueabi
sysroots
version-cortexa9hf-neon-poky-linux-gnueabi
kevin at kp-workstation in ~/sdk
$ . environment-setup-cortexa9hf-neon-poky-linux-gnueabi
kevin at kp-workstation in ~/sdk
$ cd ~/hello_world/
kevin at kp-workstation in ~/hello_world
$ ls
qt_hello_world.cpp
kevin at kp-workstation in ~/hello_world
$ qmake -project
sh: OE_QMAKE_CXX: command not found
sh: OE_QMAKE_CXXFLAGS: command not found
kevin at kp-workstation in ~/hello_world
$ arm-poky-linux-gnueabi-g++
arm-poky-linux-gnueabi-g++: fatal error: no input files
compilation terminated.

[SGaist]

Which mkspec are you using ?

[kptt]

@SGaist linux-oe-g++

[kptt]

@SGaist Looking at the build steps for my target in qtcreator, I found that the -spec option was omitted in the qmake step. I added it under additional arguments, but that didn't change anything.

[SGaist]

You should rather have a dedicated Kit where you configure that kind of stuff.

[kptt]

@SGaist Well, looking at the Details under the Qt Versions tab for my kit I do indeed see that mkspec, QMAKE_SPEC, QMAKE_XSPEC are all defined as "linux-oe-g++". That means the kit is configured for linux-oe-g++, correct?

[SGaist]

Looks good.

Did you check the makespec itself to see if there some hardcoded path ?