Re: Trouble compiling Qwt 5.1.1 with Qt 4.4.0
Brought to you by:
rathmann
From: Igor <lin...@pr...> - 2008-08-18 10:09:18
|
Uwe Rathmann pravi: > On Monday 18 August 2008 11:01, Igor wrote: > > >> qwt_designer_plugin.obj : error LNK2001: unresolved external symbol >> "public: virtual void __thiscall QwtKnob::fontChange(class QFont const >> &)" (?fontChange@QwtKnob@@EAEXABVQFont@@@Z) >> > > Sounds like a problem on your side. At least QwtKnob::fontChange hasn't > changed since decades. > I know that there is not problem with this function because I get a LOT of similar messages. And I also dont understand why this is not working. What could be wrong? > >> Does that mean I must recompile Qt with STL enabled? So does Qwt require >> STL enabled? >> > > No, it doesn't. Are you sure, that you have built the Qwt with the same Qt > environment ? > Well, I have built Qt that is now active and being used by Visual Studio Integration. Qwt Designer plugin however does not load, message says: Expected build key "Windows msvc release full-config", got "Windows msvc release full-config no-stl". Both are release, the only difference that I see here is in STL parameter. Maybe Designer needs STL built into Qt to launch Qwt plugin. However, I think the only option here is to try to rebuild Qt without "no-stl" parameter. Igor > Uwe > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > qwt-interest mailing list > qwt...@li... > https://lists.sourceforge.net/lists/listinfo/qwt-interest > > |