undefined reference to duckx::Document::Document

[jsulm]

@Toruha Please post text as text, not screen shots.
Why do you add the headers from that library directly? It is enough to set INCLUDEPATH as ayou're already doing.
Did you build the library already?

[kkoehne]

This post is deleted!

[Toruha]

@jsulm I built the library via Cmake and compiled it in Visual Studio 2019. Then I added the library as "External library" referring to https://doc.qt.io/qtcreator/creator-project-qmake-libraries.html.

[jsulm]

@Toruha What compiler do you use for your Qt application?

[Toruha]

@jsulm c++11 console

[Toruha]

@Toruha I hope this is what you were asking.

[Toruha]

Text .pro:

QT -= gui

CONFIG += c++11 console
CONFIG -= app_bundle

SOURCES +=
main.cpp

qnx: target.path = /tmp/$${TARGET}/bin
else: unix:!android: target.path = /opt/$${TARGET}/bin
!isEmpty(target.path): INSTALLS += target

win32:CONFIG(release, debug|release): LIBS += -L$$PWD/duckx/lib/ -lduckx
else:win32:CONFIG(debug, debug|release): LIBS += -L$$PWD/duckx/lib/ -lduckxd
else:unix: LIBS += -L$$PWD/duckx/lib/ -lduckx

INCLUDEPATH += $$PWD/duckx/include/duckx
DEPENDPATH += $$PWD/duckx/include/duckx

INCLUDEPATH += $$PWD/duckx/include/duckx
HEADERS +=
constants.hpp
duckx.hpp
duckxiterator.hpp
pugiconfig.hpp
pugixml.hpp
zip.h

[kkoehne]

As suggested already by @jsulm , please don't list duckx headers in HEADERS variable.

Can you paste the actual compiler output (Use Build>Rebuild, and paste the output of 'Comiple Output' pane?)

[Christian Ehrlicher]

After a short look at the duckx.hpp header file you will see that it lacks the proper import/export macros as described e.g. here. So you can either only build and link the library as static lib or add the correct macros.

[Toruha]

I got a new error trying to return everything back

[jsulm]

@Toruha said in undefined reference to duckx::Document::Document:

c++11 console

This doesn't tell me much, really!
Did you use the Microsoft compiler (same as in Visual Studio)? Or did you use MinGW?

[Toruha]

@jsulm MinGW

[jsulm]

@Toruha You can't mix different compilers like in this case Microsoft compiler and MinGW. You have to build both, the library and your app, with same compiler.

But from your screen-shot above it rather looks like you're using Microsoft compiler...

[kkoehne]

Right, the _ITERATOR_DEBUG_LEVEL, RuntimeLibrary issues above rather show that you've done a Release build of duckx, but want to use it in a debug build of your app. This won't work; you need to compile both in the same configuration.

[Toruha]

@jsulm I tried to rebuild under Microsoft compiler. What caused these new errors

[Toruha]

@jsulm Thanks, this solves the original problem

[Toruha]

@kkoehne Thanks. Everything works after changing the build type