lqt icon indicating copy to clipboard operation
lqt copied to clipboard

Unresolved external symbols

Open AdaWH opened this issue 9 years ago • 0 comments

Hey guys,

hopefully someone will see this post after the latest contribution to this project is a little back-dated :(

At first, I want to make clear what I have achieved so far:

  • I downloaded the latest source (obvioulsy) and extracted the ZIP-file
  • SInce I don't wanna use CMake, I followed the instructions in "./lqt-master/doc/no-cmake-build.txt". Everything went fine, so far, until I came to the very last point "Copy static files and compile binding".
  • I was able to perform the commands "qmake -project -template lib -o qtgui.pro" and "qmake" successfully but after that - the command "make" or "nmake" respectively - failed due to the mentioned unresolved externals.

I checked the qmake-generated files "Makefile", "Makefile.debug" and "Makefile.release" so often, I cannot even count my attempts. I changed the "qtgui.pro"-file back and forth, but nothing seemed to work.

At first I had the idea that - as it often is - a library wasn't included correctly. Each of the unresolved externals (there are about 1500 !!!! of them) has a pefix 'Q' in front, like:

qtgui_merged_build.obj:-1: Fehler: LNK2001: unresolved external symbol "public: virtual bool __thiscall QWizard::winEvent(struct tagMSG *,long *)" (?winEvent@QWizard@@UAE_NPAUtagMSG@@PAJ@Z

So I assumed it would be one of the Qt-libraries. But the Makefile has the correct path to the library directory of Qt (in my case "E:/Qt/4.6.3/lib") and QtCore.lib as well as QtGui.lib are included. I have also verified that the debug-libs are only included in Makefile.debug and that release-libs are only included in Makefile.release.

As you can see, I am using Qt Version 4.6.3 which has not been tested until now (this is at least what the documentation says ... ). Could this be an issue? I have checked some functions that have been declared as "unresolved" whether they are exported by the QtGui.dll and - surprise, surprise - they are indeed, so this usually can't be the problem here, can it?

I am developing on Windows 7 x64 platform using Visual Studio 2005th "nmake"-tool and the cl-compiler.

If anyone can help me getting rid of this issue, please do not hesitate replying to my post. Any help will be appreciated. If some kind of information is missing, please let me know and I try to update my post.

AdaWH avatar Aug 20 '14 14:08 AdaWH