Re: [Paraview] Branding branch

2010-05-17 Thread A M
Yes the ParaView Works perfectly fine! However I fixed the problem and now I can compile the examples!! I think there was two things caused this issue 1. as you mentioned I had the compiled and binary of Paraview (Two different versions) both installed on the my computer which I think

Re: [Paraview] Branding branch

2010-05-13 Thread Utkarsh Ayachit
Does ParaView itself work for you at all? Utkarsh On Wed, May 12, 2010 at 9:05 AM, A M ars...@uga.edu wrote: Dear Utkarsh yes, I meant the missing DLL issues. I ran the dependency walker. I loaded the executable file to the dependency walker (pic attached) and it seems there are 2 dlls that

Re: [Paraview] Branding branch

2010-05-11 Thread A M
As you suggested, I added the dll path (ParaView-3.8.0-bin\bin\Debug) to the environment variable as well as the Qt path, however when I ran the .exe file again I got the same error, so I added the dll files manually to the same directory as the .exe file, at first was asking about some Paraview

Re: [Paraview] Branding branch

2010-05-11 Thread Eric E. Monson
Hey Sam, Instead of trying to build those branded applications separately, did you try first to build ParaView with BUILD_EXAMPLES: ON and see if those applications are built correctly and run okay? I'm not really a Windows developer, either, but I've been able to build Release versions of

Re: [Paraview] Branding branch

2010-05-11 Thread Eric E. Monson
Hey Sam, Maybe this won't make a difference (and I don't remember where I saw to do this), but you have your PATH set to the Qt bin directory rather than the lib directory. I have some notes saying I had trouble unless the lib directory was in my PATH... -Eric On May 11, 2010, at 4:44 PM, A

Re: [Paraview] Branding branch

2010-05-10 Thread Utkarsh Ayachit
When you are running on windows, windows expects that all the dlls are in PATH (or the same location as the exe). You may want to start the clone executable from a terminal ensuring that you set the PATH environment variable correctly to point to the dlls under the ParaView build dir. Utkarsh On

[Paraview] Branding branch

2010-05-09 Thread A M
Hi! So I am a little confused! I read a paper by Utkarsh A. Ayachit and in this paper he mentioned to clone the repository at git://github.com/utkarshayachit/ParaView.git to obtain the modified ParaView source, up to here it is just fine, I can clone the directory just fine. Then he goes on and

Re: [Paraview] Branding branch

2010-05-09 Thread Utkarsh Ayachit
You might also want to refer to the following wiki page details on the custom application components: http://paraview.org/Wiki/Writing_Custom_Applications Utkarsh On Sun, May 9, 2010 at 9:48 PM, David E DeMarle dave.dema...@kitware.com wrote: Since that time, the branding infrastructure has