The magic behind library names is implemented in the functions qtLibraryTarget and qtAddLibrary, that are part of the feature files of your Qt installation.
Uwe
The magic behind library names is implemented in the functions qtLibraryTarget and qtAddLibrary, that are part of the feature files of your Qt installation.
Uwe
gkarthick5 (3rd August 2011)
gkarthick5,
I came across a similar problem myself, so I wonder if you found a solution for your problem?
I have a similar problem.
In my platform qmake.conf there is QT_LIBINFIX set to 4.
Building Qwt produced qwt.dll.
But when I try to build my project it tries to link to qwt4.
If I understand it correctly, the build system should have produced 'qwt4.dll', not 'qwt.dll'.
I found that qwtAddLibrary function adds infix to the name, while the qwtLibraryTarget does not. How can this possibly work? Is this not an inconsistency?
It is similar way in both customised qwt's qwtfunctions.pri and standard qt_functions.prf.
I am not sure if this is a misconfiguration in Qt or Qwt so not sure where to look for a fix.
I tried to comment out QT_LIBINFIX definition in qmake.conf but it affects all libraries and tries to link to 'QtCore' instead of 'QtCore4' for example.
Meanwhile I modified qwtAddLibrary in qwt's qwtfunctions.pri to not to take infix into account. I realise this is not correct but at least I can now carry on working on a project.
Any help or suggestion will be very much appreciated.
I use Qt 4.8.5 and Qwt 6.1.0 with mingw-w64 cross compiler.
Last edited by Stas1; 11th December 2013 at 19:56.
IIRC this has been fixed in SVN ( trunk and 6.1 branch ) some time ago.
Uwe
Uwe, thank you. I found the fix in 6.1 branch in SVN. For anybody interested, here is the relevant commit: http://sourceforge.net/p/qwt/code/1771/
Bookmarks