Building application with Qwt 6.1.0

[Uwe]

Disable "CONFIG += silent" in your project file ( if set ) and have a look at the commands, when compiling your files. Do you see the path to the Qwt include directory there ?

Uwe

[frankiefrank]

Thanks for answering Uwe.

I don't have -silent set, but I'm not sure where I should be seeing the path.

My .pro file has

QT       += core gui xml script declarative network
greaterThan(QT_MAJOR_VERSION, 4): QT += widgets
 
TARGET = MyAppCore
TEMPLATE = app
 
CONFIG += qwt

QT       += core gui xml script declarative network
greaterThan(QT_MAJOR_VERSION, 4): QT += widgets

TARGET = MyAppCore
TEMPLATE = app

CONFIG += qwt

To copy to clipboard, switch view to plain text mode 

(I skipped the sources/headers/forms part)

I'm running qMake and building via Qt Creator (2.7.2).

When I go to the project properties I see:
"effective qMake call":
qmake.exe D:\MyAppCore\MyAppCore.pro -r -spec win32-msvc2010 "CONFIG+=debug" "CONFIG+=declarative_debug" "CONFIG+=qml_debug"

After that it runs a make step with jom.exe.

My output starts with:

Starting: "C:\Qt\Qt5.1.0\Tools\QtCreator\bin\jom.exe"
C:\Qt\Qt5.1.0\Tools\QtCreator\bin\jom.exe -f Makefile.Debug
cl -c -nologo -Zm200 -Zc:wchar_t -Zi -MDd -GR -W3 -w34100 -w34189 -EHsc -DUNICODE -DWIN32 -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_DECLARATIVE_LIB -DQT_WIDGETS_LIB -DQT_NETWORK_LIB -DQT_SCRIPT_LIB -DQT_XML_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I"C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\include" -I"C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\include\QtDe clarative" -I"C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\include\QtWi dgets" -I"C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\include\QtNe twork" -I"C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\include\QtSc ript" -I"C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\include\QtXm l" -I"C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\include\QtGu i" -I"C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\include\QtCo re" -I"debug" -I"." -I"." -I"C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\mkspecs\win3 2-msvc2010" -Fodebug\ @C:\Users\myusername\AppData\Local\Temp\myproject. obj.5900.405.jom

I really don't see the Qwt folder here.

[Uwe]

I really don't see the Qwt folder here.

Yes, indicating that "CONFIG += qwt" didn't work because your qmake is not configured properly ( you can prove this easily by replacing "CONFIG += qwt" by "include ( C:\Qwt-6.1.0\features\qwt.prf )".

You wrote, that you have set QMAKEFEATURES - what exactly is the output of "qmake -query QMAKEFEATURES" and are you sure, that this is the same qmake version as it is used by the creator ?

Uwe

[frankiefrank]

That's helpful. I see that the Qt Versions tab lists the qmake from the "bin" folder. I went with cmd.exe to that path, and it still looks ok.

C:\Qt\Qt5.1.0\5.1.0\msvc2010_opengl\bin>qmake -query QMAKEFEATURES
C:\Qwt-6.1.0\features

Update: I'm doing this from the Visual Studio 2008 command line prompt. QMAKE with the above settings, the query seems ok but "nmake" doesn't contain any Qwt paths.

[Uwe]

What happens, when you replace "CONFIG += qwt" by the include statement above ?

Uwe

[frankiefrank]

I get this error:

moc_MyPlot.obj:-1: error: LNK2001: unresolved external symbol "public: static struct QMetaObject const QwtPlot::staticMetaObject" (?staticMetaObject@QwtPlot@@2UQMetaObject@@B)

[Uwe]

As "CONFIG += qwt" is only another way for including the installed qwt.prf you definitely have a problem with your QMAKEFEATURES setting. As everything you wrote in this thread looks o.k. to me something has to be wrong with what you have not written so far.
Concerning the link error: how does a compile and the link commands look like ?

Uwe

[frankiefrank]

Thanks for your reply and help so far!

I don't really know how else to check the QMAKEFEATURES. If I run the Qt 5.1 command prompt and try qmake -query qmakefeatures I get the correct path.

I now think I'm ok, but I did several things:

I took the advice from another post where you left a compliment on:
http://www.qtcentre.org/threads/5378...3-(Win7-64bit)

And added the Qwt-6.1.0\lib folder to my PATH variable. I also added the QMAKEFEATURES setting to the qmake "additional arguments" in Qt Creator. I then managed to build.

I'm not sure where the mess is coming from, hope I'm ok now.