[Paraview] VTKEdge compilation on Windows 32bit

[Lucy Gagliardi]

Hi Utkarsh,

 

I have been trying to compile VTKEdge Paraview plugin for 3.6.1 on
windows XP using visual C++ express 2005. The build appears to be
successful (no warnings or errors) however the VTKEdge.dll is not
present in the build directory (only the debug directory created by
VC++). 

 

Previously, I have successfully compiled the same source (Paraview 3.6.1
and VTKEdge) on linux with no issues. I will try the CVS Paraview when I
get a chance and report back. 

 

Thanks,

 

Lucy

 

________________________________

From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 30 October 2009 16:54
To: Lucy Gagliardi
Cc: Berk Geveci; paraview at paraview.org
Subject: Re: [Paraview] VTKEdge compilation on Windows 32bit

 

Lucy,

 

So you are trying to build VTKEdge with Paraview 3.6.1, is that correct?
Are you sure the build is succeeding? If I am not mistaken, the ParaView
plugin in VTKEdge uses features that were added to CVS ParaView (that
aren't present in 3.6.* releases) and hence it cannot work with 3.6
releases. Try using CVS ParaView.

 

Utkarsh

 

On Fri, Oct 9, 2009 at 9:55 AM, Lucy Gagliardi <lgagliardi at brawngp.com>
wrote:

Hi Berk,

 

Thanks for your reply, 

 

This is a fresh install with neither Qt nor PV having been previously
installed on the system, so I'm fairly sure there are no conflicts. I
compiled 3.6.1 using VC++ just prior to starting the VTKEdge
compilation, with the same CMake version and Qt libraries.

 

Thanks,

 

Lucy

 

 

________________________________

From: Berk Geveci [mailto:berk.geveci at kitware.com] 
Sent: 09 October 2009 14:22
To: Lucy Gagliardi
Cc: paraview at paraview.org
Subject: Re: [Paraview] VTKEdge compilation on Windows 32bit

 

Hi Lucy,

Note: Utkarsh, who wrote all of the ParaView plugins in VTKEdge, is on
vacation for 3 weeks. It is unlikely that you will get a response from
him until he is back.

I don't have a lot of experience with Windows either. Are you sure the
Qt version and the compiler you are using are matching the one ParaView
was compiled with? This has been one of the major source of
compatibility issues in the past.

-berk

On Fri, Oct 9, 2009 at 6:09 AM, Lucy Gagliardi <lgagliardi at brawngp.com>
wrote:

Hi,

 

I've been trying to compile the VTKEdge Paraview plugin on windows using
VC++ 2005 Express. However, I don't seem to be getting the VTKEdge.dll
appearing in my bin dir after install.

It does appear in a release dir which appears in the bin due to the
visual studio compilation, but if I try to link to this in Paraview, I
get an error stating that it is not a valid Qt plugin. 

I have successfully installed the same source on linux, with no issues,
but I have very little experience of windows compilations. I've attached
my CMakeCache.txt in case there's something I might be missing.

 

Can anyone help?

 

Thanks in advance,

 

Lucy

 

 

 

Lucy Gagliardi
CFD Engineer



 

 

T + 44 (0)1280 846880

www.BrawnGP.com <http://www.brawngp.com/> 

 

Brawn GP Limited. Registered in England No. 787446.

Registered Office at Brawn GP Formula One Team, Brackley, Northants NN13
7BD.

 

Please consider the environment before printing this email

 

 


_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

 


_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20091103/49f448ce/attachment-0001.htm>