[Paraview] ParaView 3 Compile Issues [CVS Head]

[Moreland, Kenneth]

Both.  There are often changes to the API between minor releases of Qt,
and if they run over something that ParaView is using, it makes it very
difficult to support both.  But more importantly, we simply do not have
the resources to support multiple versions of Qt.  With changes in bugs
and features in Qt, it becomes too hard to determine if a problem lies
with Qt, ParaView, or a combination of both.  Thus, we limit ourselves
to one version of Qt at a time.  If you want to use a different version,
I am afraid you are on your own.

-Ken

> -----Original Message-----
> From: paraview-bounces+kmorel=sandia.gov at paraview.org
[mailto:paraview-
> bounces+kmorel=sandia.gov at paraview.org] On Behalf Of Mike Jackson
> Sent: Wednesday, July 18, 2007 8:25 AM
> To: Berk Geveci
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] ParaView 3 Compile Issues [CVS Head]
> 
> Is the "support" for Qt 4.3 because no one is testing against Qt 4.3
> or because there is API breakage between 4.2.3 and 4.3? I asked
> because on both windows xp and OS X this was the only way I can get a
> stable ParaView 3.1.0 to compile with our code...
> 
> 
> --
> Mike Jackson   Senior Research Engineer
> Innovative Management & Technology Services
> 
> 
> On Jul 18, 2007, at 10:10 AM, Berk Geveci wrote:
> 
> > By the way, we do not support Qt 4.3.0 yet. You should be using
4.2.3.
> >
> > -berk
> >
> > On 7/2/07, Mike Jackson <imikejackson at gmail.com> wrote:
> >> It seems the "problem" is in the "VTK_USE_RPATH" setting. If I set
> >> this to OFF (which is the default) then I end up with a broken
build
> >> and the "paraview-real.app". If I set this to "ON" then I end up
with
> >> a good build and a paraview.app that actually runs. I guess the
> >> CMakeLists.txt files still need some work. This was built against
Qt
> >> 4.3.0 as Dylibs. I am going to try again with Qt 4.3.0 as
Frameworks.
> >>
> >>
> >> --
> >> Mike Jackson   Senior Research Engineer
> >> Innovative Management & Technology Services
> >>
> >>
> >> On Jul 1, 2007, at 12:53 PM, Marc Baaden wrote:
> >>
> >> >
> >> > Hi again,
> >> >
> >> > imikejackson at gmail.com said:
> >> >>> Marc. thanks for the links. I am basically doing the same thing
> >> >>> except that I am using Qt 4.3.0.
> >> >
> >> > Ah, yes, I hadn't noticed that the QT versions differed. I don't
> >> > remember why I used 4.2.3 and not 4.3.0.
> >> >
> >> >
> >> >>> I get a bin/paraview-real.app but only a bin/paraview which
will
> >> >>> actually run which is at least partially good, but where is my
> >> >>> paraview.app going?
> >> >
> >> > Where does the *-real come from? I don't get such a thing. Just a
> >> > plain
> >> > paraview.app! And I don't get a bin/paraview executable at all.
> >> > As I said, the paraview.app builds fine.
> >> >
> >> > If that is any help to you, I could certainly tar my src or build
> >> > directories and send them to you..
> >> >
> >> > Good luck,
> >> >   Marc
> >> >
> >> > --
> >> >  Dr. Marc Baaden  - Institut de Biologie Physico-Chimique, Paris
> >> >  mailto:baaden at smplinux.de      -      http://www.baaden.ibpc.fr
> >> >  FAX: +33 15841 5026  -  Tel: +33 15841 5176  ou  +33 609 843217
> >> >
> >> >
> >>
> >> _______________________________________________
> >> ParaView mailing list
> >> ParaView at paraview.org
> >> http://www.paraview.org/mailman/listinfo/paraview
> >>
> >
> >
> > --
> > Berk Geveci
> > Kitware Inc.
> > 28 Corporate Drive
> > Clifton Park, NY, 12065
> 
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview