<![CDATA[undefined reference to duckx::Document::Document]]>I'm trying to add a library to a project. https://github.com/AlexanderVatov/DuckX. Using qmake.
I encountered the following errors when executing the test code proposed by the author of the library:

alt text

.pro file looks like this:

alt text

To solve the problem, I tried to rebuild the project.

]]>https://forum.qt.io/topic/134976/undefined-reference-to-duckx-document-documentRSS for NodeFri, 01 May 2026 21:11:07 GMTFri, 11 Mar 2022 09:33:43 GMT60<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 12:46:46 GMT]]>@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...

]]>https://forum.qt.io/post/706065https://forum.qt.io/post/706065Fri, 11 Mar 2022 12:46:46 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Sat, 12 Mar 2022 14:32:59 GMT]]>@kkoehne Thanks. Everything works after changing the build type

]]>https://forum.qt.io/post/706151https://forum.qt.io/post/706151Sat, 12 Mar 2022 14:32:59 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Sat, 12 Mar 2022 14:21:42 GMT]]>@jsulm Thanks, this solves the original problem

]]>https://forum.qt.io/post/706150https://forum.qt.io/post/706150Sat, 12 Mar 2022 14:21:42 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Sat, 12 Mar 2022 13:28:24 GMT]]>@jsulm I tried to rebuild under Microsoft compiler. What caused these new errors

]]>https://forum.qt.io/post/706147https://forum.qt.io/post/706147Sat, 12 Mar 2022 13:28:24 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 13:11:32 GMT]]>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.

]]>https://forum.qt.io/post/706070https://forum.qt.io/post/706070Fri, 11 Mar 2022 13:11:32 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 12:46:46 GMT]]>@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...

]]>https://forum.qt.io/post/706065https://forum.qt.io/post/706065Fri, 11 Mar 2022 12:46:46 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 12:44:47 GMT]]>@jsulm MinGW

]]>https://forum.qt.io/post/706064https://forum.qt.io/post/706064Fri, 11 Mar 2022 12:44:47 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 12:34:04 GMT]]>@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?

]]>https://forum.qt.io/post/706059https://forum.qt.io/post/706059Fri, 11 Mar 2022 12:34:04 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 12:33:39 GMT]]>I got a new error trying to return everything back
5575e08c-05a1-4c3a-8fc1-dab30f61ae2a-image.png

]]>https://forum.qt.io/post/706058https://forum.qt.io/post/706058Fri, 11 Mar 2022 12:33:39 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 12:06:43 GMT]]>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.

]]>https://forum.qt.io/post/706053https://forum.qt.io/post/706053Fri, 11 Mar 2022 12:06:43 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 11:48:27 GMT]]>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?)

]]>https://forum.qt.io/post/706051https://forum.qt.io/post/706051Fri, 11 Mar 2022 11:48:27 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Sat, 12 Mar 2022 13:26:25 GMT]]>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

]]>https://forum.qt.io/post/706050https://forum.qt.io/post/706050Sat, 12 Mar 2022 13:26:25 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 11:32:53 GMT]]>@Toruha I hope this is what you were asking.

]]>https://forum.qt.io/post/706047https://forum.qt.io/post/706047Fri, 11 Mar 2022 11:32:53 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 11:20:24 GMT]]>@jsulm c++11 console

]]>https://forum.qt.io/post/706046https://forum.qt.io/post/706046Fri, 11 Mar 2022 11:20:24 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 11:08:32 GMT]]>@Toruha What compiler do you use for your Qt application?

]]>https://forum.qt.io/post/706045https://forum.qt.io/post/706045Fri, 11 Mar 2022 11:08:32 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 10:58:07 GMT]]>@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.

]]>https://forum.qt.io/post/706043https://forum.qt.io/post/706043Fri, 11 Mar 2022 10:58:07 GMT<![CDATA[Reply to undefined reference to duckx::Document::Document on Fri, 11 Mar 2022 10:21:25 GMT]]>@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?

]]>https://forum.qt.io/post/706041https://forum.qt.io/post/706041Fri, 11 Mar 2022 10:21:25 GMT