[Paraview] Forcing a Qt version
Dominik Szczerba
dominik at itis.ethz.ch
Tue Oct 7 15:24:57 EDT 2008
Yeah I used to fight with it too. It is far from clean. I do not recall now
the details, but what did the trick for me was to specify QMAKE_EXECUTABLE
(or something) and QT_DESIRED_VERSION (or something)
Dominik
On Tuesday 07 October 2008 05:11:56 pm Renato N. Elias wrote:
> Michael and Clinton
>
> I guess I'm facing a CMake's bug. I'm actually working with two Qt4
> versions: Qt 4.4.2 (official distribution, including VS2008 integration)
> and Qt 4.3.4 (open source distribution). I've set the QTDIR variable as
> Michael suggested (in two places. Firstly in my own environment
> variables and secondly in the system's variables) but it had not worked.
> After that I downgraded CMake to 2.6.2 (official release), same problem.
>
> Clinton, setting the QT_QMAKE_EXECUTABLE in CMake was the first thing I
> tried (take a look at here
> http://www.nacad.ufrj.br/~rnelias/paraview/qt.JPG). It should be the
> easiest way. CMake keeps my set but mix with the other Qt stuffs with
> the newest version (4.4.2). Thus, when I try to launch the compiled PV I
> get an error message saying that it's not possible to find the entry
> point of the procedure ?focusNextPrevChild at QGraphicsView@@MAE_N_N at Z in
> dynamic library QtGui4.dll. My guess, is that Visual Studio is "qmaking"
> with version 4.3.4 and linking against 4.4.2.
>
> By the way, should PV3 work with 4.4.2? Has anybody tried it?
>
> Regards
>
> Renato
>
> Clinton Stimpson wrote:
> > If there's a qmake in your PATH, it takes precedence over whatever you
> > set QTDIR to be.
> > By the way, the use of QTDIR has been deprecated by Trolltech.
> > Another thing you can do is set QT_QMAKE_EXECUTABLE in the cmake-gui
> > before you hit configure for the first time, and it won't matter what
> > your PATH is.
> >
> > Clint
> >
> > Michael Jackson wrote:
> >> Renato
> >> Assuming you really meant Qt 4.3.4 and NOT Qt 3.3.4 here is what
> >> you need to do.
> >>
> >> Remove everything from your build directory so we can start clean.
> >> Go to "My Computer" and add/check/set the QTDIR (Capitalization
> >> counts) to your Qt 4 installation.
> >> Launch CMakeSetup or CMake-GUI.exe and configure ParaView. You should
> >> at most get a warning about the version of Qt your are using and the
> >> "required" version.
> >>
> >> Everything _should_ work.
> >>
> >> Now, if you are really trying to use Qt 3 instead of Qt 4 then that
> >> is not supported. YOu need at least Qt 4.3 to build ParaView.
> >>
> >> Mike Jackson
> >>
> >> On Oct 7, 2008, at 10:31 AM, Renato N. Elias wrote:
> >>> Hi Michael,
> >>>
> >>> there's something overriding my QTDIR because CMake still points to
> >>> the wrong Qt version. I've set both QT_QMAKE_EXECUTABLE and QTDIR to
> >>> 3.3.4 version, but CMake still returns me a warning that I'm using
> >>> an unsupported version of Qt. Now I'm trying to understand all that
> >>> CMake sintaxe in FindQt4.cmake and UseQt4.cmake modules.
> >>>
> >>> weird, isn't it?!
> >>>
> >>> Renato.
> >>>
> >>> Michael Jackson wrote:
> >>>> On Oct 7, 2008, at 9:26 AM, Renato N. Elias wrote:
> >>>>> Hi folks,
> >>>>>
> >>>>> I'm facing a curious problem here. I was using Qt-4.3.4 to compile
> >>>>> ParaView in a Windows machine and it had been working fine but
> >>>>> after installing a second version of Qt (4.4.2), CMake 2.6 (patch
> >>>>> 2 RC-5) seems to be getting confused about which version it should
> >>>>> use. Even pointing QT_QMAKE_EXECUTABLE to Qt-4.3.4, CMake insists
> >>>>> in pointing all other stuffs to Qt-4.4.2 paths (QT_DOC_DIR,
> >>>>> QT_INCLUDE_DIR, QT_LIBRARY_DIR and so on...). In my environment I
> >>>>> have set QT_QMAKE_EXECUTABLE to Qt-4.3.4 but it's not solving the
> >>>>> problem. Is there any other environment variable that could be
> >>>>> used to force CMake in using the correct version of Qt?
> >>>>>
> >>>>> Regards
> >>>>>
> >>>>> Renato.
> >>>>> _______________________________________________
> >>>>> ParaView mailing list
> >>>>> ParaView at paraview.org
> >>>>> http://www.paraview.org/mailman/listinfo/paraview
> >>>>
> >>>> You can set QTDIR to the installation directory. CMake will try to
> >>>> use that variable if it finds it. Also, once the Qt libraries and
> >>>> stuff is set in a build directory it is pretty hard to get it to
> >>>> change. Clearing the build directory and starting out again with
> >>>> the QTDIR env variable set should help you find the correct version.
> >>>>
> >>>> Alternately you can open the CMakeCache.txt and remove all traces
> >>>> of ANY variable with QT in its name. This isn't exactly the
> >>>> preferred way to trouble shoot this problem but has worked in the
> >>>> past, plus saves all your compiled code from having to be recompiled.
> >>>>
> >>>>
> >>>> Mike Jackson
> >>>> _______________________________________________
> >>>> ParaView mailing list
> >>>> ParaView at paraview.org
> >>>> http://www.paraview.org/mailman/listinfo/paraview
> >>>
> >>> _______________________________________________
> >>> ParaView mailing list
> >>> ParaView at paraview.org
> >>> http://www.paraview.org/mailman/listinfo/paraview
> >>
> >> _______________________________________________
> >> ParaView mailing list
> >> ParaView at paraview.org
> >> http://www.paraview.org/mailman/listinfo/paraview
> >
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
--
Dominik Szczerba, Ph.D.
Computational Physics Group
Foundation for Research on Information Technologies in Society
http://www.itis.ethz.ch
More information about the ParaView
mailing list