[Paraview-developers] [paraview-developers] Do I have to build ParaView Development from the source code if I want to add my new plug-in?

[Mingcheng Chen]

Oops I am sorry. I just click reply....

So the path "Q:\4.6.3\lib" actually could represent "C:\Qt\4.6.3\lib",
right?

Unfortunately I found there is only Qt4.6.3VS2008 in
ftp://ftp.trolltech.no/qt/source/, which means I need to build my own Qt,
right?

Thanks again!

Best regards,
Mingcheng Chen
January 30th, 2012

On Mon, Jan 30, 2012 at 3:29 PM, David E DeMarle
<dave.demarle at kitware.com>wrote:

> Please keep discussion on the mailing list so everyone can contribute
> and benefit.
>
> I think you have to install qt 4.6.3. If the libraries used by the pv
> libs and your program don't match, it can not link and run.
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
>
> On Mon, Jan 30, 2012 at 4:24 PM, Mingcheng Chen <linyufly at gmail.com>
> wrote:
> > Hi David,
> >
> > When I was compiling my plugin with 32 bit ParaView Development 3.12.0
> > downloaded from the link you provided, I encountered the follow error
> > report.
> >
> > LINK : fatal error LNK1181: cannot open input file
> > 'Q:\4.6.3\lib\QtWebKit4.lib'.
> >
> > However the available Qt is in C:\Qt\4.8.0 on my machine.
> >
> > How can I change that path?
> >
> > Thanks!
> >
> > Best regards,
> > Mingcheng Chen
> > January 30th, 2012
> >
> >
> > On Mon, Jan 30, 2012 at 8:42 AM, David E DeMarle <
> dave.demarle at kitware.com>
> > wrote:
> >>
> >> On Wed, Jan 25, 2012 at 11:05 PM, Mingcheng Chen <linyufly at gmail.com>
> >> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> The latest release version of ParaView Development is 3.8. Compiling my
> >>> plug-in with it always returns: error MSB6006: "cmd.exe" exited with
> code 1.
> >>>
> >>> However, I can successfully compile my plug-in with ParaView
> Development
> >>> 3.12 which was built by myself from the source code. (I once asked
> about an
> >>> MPI related problem when building ParaView from source code. I did not
> solve
> >>> the problem, so I just disabled USE_MPI.)
> >>>
> >>
> >> If you need your plugins to work with the official ParaView binaries,
> >> first try the development libs from
> >>
> http://paraview.org/Wiki/ParaView:Plugin_Deployment_with_Development_Installs
> >> (Thanks blueCAPE Lda for making the 3.12 versions!).
> >>
> >> If those don't work for you then yes you need to build your own and you
> >> must make sure your build environment matches the build environment we
> used
> >> to make the binaries
> >> See: http://www.paraview.org/Wiki/ParaView_Binaries
> >>
> >>
> >>>
> >>> Now I had a more challenging task: install a parallel ParaView on a
> >>> remote multi-core machine which has no GPU and which should be able to
> be
> >>> added my new plug-ins to.
> >>>
> >>> The remote multi-core machine has Visual Studio 2010 and a 64-bit
> Windows
> >>> operating system.
> >>>
> >>> As far as I know, for the absence of GPU, I need to install Mesa3D,
> >>> right? For MPI, is MPICH2 enough? For Qt library, is any version for
> VS2010
> >>> acceptable?
> >>>
> >>
> >> On windows you don't typically need Mesa, the Windows GL drivers should
> >> handle it.
> >>
> >> Either MPICH2 and OpenMPI should work. I've been using MPICH myself
> >> lately.
> >>
> >> Check the Qt download site. If they don't have a VS2010 version you will
> >> have to build it from source yourself.
> >>
> >>
> >>> Is there any cutoff for me?
> >>>
> >>> I am looking forward to helping hand badly...
> >>>
> >>> Thanks for finishing reading!
> >>>
> >>> Best regards,
> >>> Mingcheng Chen
> >>> January 25th, 2012
> >>>
> >>
> >> David E DeMarle
> >> Kitware, Inc.
> >> R&D Engineer
> >> 21 Corporate Drive
> >> Clifton Park, NY 12065-8662
> >> Phone: 518-881-4909
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20120130/3481fbee/attachment.htm>