Build problems Nokia QT SDK 1.1

[alehtola]

hello,

I'm experimenting with QT SDK with following example.

http://doc.qt.nokia.com/qtcreator-2....e-example.html

It works on simulator and in real device (N97) as expected.

My problem comes valid when I try to add a new class into project. After many experiments I end up adding simplest possible QObject derived class via Creator wizard "Add new"->c++->c++ class.

c/p headerfie.

#ifndef MYTESTCLASS_H
#define MYTESTCLASS_H

#include <QObject>

class MyTestClass : public QObject
{
Q_OBJECT
public:
explicit MyTestClass(QObject *parent = 0);

signals:

public slots:

};

#endif // MYTESTCLASS_H

As soon I declare this class in my existing BatteryIndicator class, Symbian build starts to fail in "rebuild all"
(simulator build works)

..
#include "mytestclass.h"

..
private:
MyTestClass testclass;

....

/NokiaQTSDK/Omat/BatteryIndicator/batteryindicator.cpp:6: error: undefined reference to `MyTestClass::MyTestClass(QObject*)'
/NokiaQTSDK/Omat/BatteryIndicator/batteryindicator.cpp:6: error: undefined reference to `MyTestClass::MyTestClass(QObject*)'
/NokiaQTSDK/Symbian/SDK/EPOC32/BUILD/NokiaQTSDK/Omat/BatteryIndicator/BATTERYINDICATOR_0XEB0275F9/GCCE/UDEB/batteryindicator.o:: In function `~MyTestClass':
/NokiaQTSDK/Omat/BatteryIndicator/mytestclass.h:7: error: undefined reference to `vtable for MyTestClass'

I found a post http://bugreports.qt.nokia.com/browse/QTSDK-98
that steps I did already.

What I might miss here, I noticed that there have been similar kind of threads on this forum but couldnt find a solution for my case though

I appreciate any help.

thanks

ari

[alehtola]

Should be SDK 1.0

[divanov]

Make sure that you have something like this in project file:

HEADERS += mytestclass.h

[alehtola]

Make sure that you have something like this in project file:

HEADERS += mytestclass.h

Wizard have added that on my behalf, whole pro-file looks like this:

QT += core gui


TARGET = BatteryIndicator
TEMPLATE = app


SOURCES += main.cpp\
batteryindicator.cpp \
mytestclass.cpp

HEADERS += batteryindicator.h \
mytestclass.h

FORMS += batteryindicator.ui

CONFIG += mobility

MOBILITY = systeminfo

symbian {
TARGET.UID3 = 0xeb0275f9
# TARGET.CAPABILITY +=
TARGET.EPOCSTACKSIZE = 0x14000
TARGET.EPOCHEAPSIZE = 0x020000 0x800000
}

[divanov]

Then clean the project and rebuild it again.
In console it's done with a commands

qmake distclean
qmake
make

Should be possible from Qt Creator also.

[danhicksbyron]

It looks like it's not the header that's missing but rather the module.

SOURCES += mytestclass.cpp

[divanov]

It looks like it's not the header that's missing but rather the module.

SOURCES += mytestclass.cpp

It is there as well.

[danhicksbyron]

That said, it's the linker step that's objecting. Does your cpp file define MyTestClass::MyTestClass(QObject*)?

[danhicksbyron]

You say

(simulator build works)

Have you tried "cleaning" the device build?

[alehtola]

Hello,

Thanks for getting me on right track. I needed to run qmake separately each time I added new class. When I created initial project containing only one class qmake is run by the Creator by default but later this does not seem happen. Qmake needs to be run either via command prompt or via build-menu. Cleaning (all) has no effect, i.e it does not force Creator for running qmake but qmake needs to run explicitly. Simulator build seems working diffrently requiring no manual qmake in this phase.

[divanov]

I needed to run qmake separately each time I added new class.

In principle this is not true Makefile checks for timestamp of .pro file and run qmake in case .pro file is newer than Makefile.

Cleaning (all) has no effect, i.e it does not force Creator for running qmake but qmake needs to run explicitly.

Note that there is a difference between make clean and make distclean, the former doesn't remove Makefile.

[alehtola]

I double checked this by new project and this is really a case. In my opinion this is a kind of bug, IDE should handle this by default.

[Tuomo]

I have also faced similar problems. From time to time I have to run qmake manually after Qt Creator just says something like "configuration unchanged, skipping qmake step".

[divanov]

Do you have any clock skew?

[danhicksbyron]

I double checked this by new project and this is really a case. In my opinion this is a kind of bug, IDE should handle this by default.

I've seen this occasionally, with both Carbide and Qt Creator, but it never was consistent (though it seems to happen more on some projects than others).