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 are missing however I searched for them and nothing > showed up on my computer! > Also you mentioned in your previous email that the path should point to this > dlls, i have the environment variable path set to the folder where all the > dlls the program is asking for are there but still get the same error. > > > best > ~A > > On Tue, May 11, 2010 at 5:50 PM, Utkarsh Ayachit > <utkarsh.ayac...@kitware.com> wrote: >> >> What do you mean by it does not work? Missing DLLs still? Did you try >> running the dependency walker to determine which dlls are missing? >> Ensure that your PATH has those missing dlls. >> >> Utkarsh >> >> On Tue, May 11, 2010 at 3:28 PM, A M <ars...@uga.edu> wrote: >> > Thanks eric >> > >> > >> > I added the Qt lib path to the PATH too but it didn't really make any >> > difference either! I am just installing netbeans on the linux system I >> > have >> > here to see if I can compile and run paraview and the examples, it might >> > work I don't know! >> > >> > best! >> > ~A >> > >> > On Tue, May 11, 2010 at 4:52 PM, Eric E. Monson <emon...@cs.duke.edu> >> > wrote: >> >> >> >> 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 M wrote: >> >> >> >> Dear David and Eric >> >> >> >> Thanks for the comments, >> >> Davie: >> >> >> >> I added the path to the environment variable in VS and I still have the >> >> same issue. I wrote something like this >> >> >> >> PATH=C:\Program Files\CMake 2.6\bin; C:\Qt\4.6.2\bin;C:\Program >> >> Files\ParaView\bin ;%PATH% >> >> this is what I think you meant. >> >> >> >> Eric: >> >> I did that already (I mean compiling Paraview with the examples and >> >> BUILD_EXAMPLES: ON) I still get the same error, I almost tried any >> >> trick in >> >> the book you can imagine! the PATH variable in my use environment >> >> variable >> >> looks like the flowing: >> >> >> >> C:\Program Files\CMake 2.6\bin; >> >> C:\Qt\4.6.2\bin >> >> C:\Program Files\ParaView\bin ; >> >> plus some other stuff not related to paraview, which seems pretty >> >> normal >> >> to me, however I got the same errors as before! it does not find the >> >> dll >> >> files. >> >> >> >> I honestly don't know what to do anymore. The only solution I can think >> >> of >> >> right now is to switch to Linux operating system instead of windows, >> >> and >> >> that doesn't necessarily means that problem would be solved either, >> >> >> >> >> >> best! >> >> ~sam >> >> >> >> On Tue, May 11, 2010 at 2:12 PM, Eric E. Monson <emon...@cs.duke.edu> >> >> wrote: >> >>> >> >>> 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 the Example applications and my own branded app on >> >>> Windows 7 64-bit. (I run them from the bin/Release directory under my >> >>> build >> >>> directory.) I used Qt 4.6.2 that I compiled myself with VS 64-bit >> >>> compiler, >> >>> Visual Studio 2008 Pro, CMake 2.8.1 and Python 2.6. >> >>> My PATH variable is very minimal, I think only the Qt library entry is >> >>> used to help configure the ParaView build: >> >>> >> >>> >> >>> %USERPROFILE%\Programming\qt-everywhere-opensource-src-4.6.2\lib;"C:\Program >> >>> Files (x86)\CMake 2.8\bin";C:\Python26;C:\Program Files (x86)\VTK\bin >> >>> (the VTK part at the end is just so my separate vtk python stuff runs >> >>> okay) >> >>> Sorry to hear you're having so much trouble. All of us run into these >> >>> strange things sometimes, but just so you know, it should work without >> >>> any >> >>> manual copying of libraries, etc. >> >>> Good luck, >> >>> -Eric >> >>> ------------------------------------------------------ >> >>> Eric E Monson >> >>> Duke Visualization Technology Group >> >>> >> >>> On May 11, 2010, at 1:05 PM, Dave Partyka wrote: >> >>> >> >>> To set the PATH when debugging from the IDE: >> >>> 1. Right click the project and select Properties >> >>> 2. In the tree view on the left select Debugging >> >>> 3. In the main panel there will be an entry called 'Environment' >> >>> 4. Set the Path by entering something like: >> >>> PATH=C:\Path\To\Something;%PATH% >> >>> >> >>> On Tue, May 11, 2010 at 12:28 PM, Utkarsh Ayachit >> >>> <utkarsh.ayac...@kitware.com> wrote: >> >>>> >> >>>> Well, unfortunately, the DLL mess is a Windows OS thing. I am not a >> >>>> regular Windows developer so I cannot tell you exactly how to access >> >>>> that option, but Visual Studio does have an option somewhere that >> >>>> allows you to specify the environment in which the application is >> >>>> running. There you can set the PATH to include the ParaView bin/debug >> >>>> (or bin/release as the case maybe) and Qt dirs. >> >>>> >> >>>> You might want to download dependency walker >> >>>> (http://www.dependencywalker.com/), a handy utility to determine >> >>>> exactly what dlls are being used/not found etc. Use this to ensure >> >>>> that correct versions of the dlls are being imported. >> >>>> >> >>>> I'd refrain from copying over dlls, this often leads to user-related >> >>>> errors down the line. >> >>>> >> >>>> As far as the missing symbol error goes, it's possible your program >> >>>> is >> >>>> accidentally bringing in a mismatched vtkCommon dll. Do you have >> >>>> other >> >>>> VTK / ParaView builds in your PATH? Use the dependency walker to >> >>>> ensure that it's using the correct vtkCOmmon (and other) dlls. >> >>>> >> >>>> Hope that helps. >> >>>> >> >>>> Utkarsh >> >>>> >> >>>> >> >>>> On Tue, May 11, 2010 at 3:17 PM, A M <ars...@uga.edu> wrote: >> >>>> > >> >>>> > 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 >> >>>> > dlls and the some Qt dlls (I have both of this added to the use >> >>>> > path >> >>>> > enviroment variable!) and then asked form some vtk dlls, the last >> >>>> > error >> >>>> > which I can not get passed of is asking for vtkCommon.dll, I added >> >>>> > the >> >>>> > dll >> >>>> > to the directory and I got this: >> >>>> > >> >>>> > " the procedure entry point >> >>>> > ?computepointforext...@vtkstructureddata@@saq...@z could not be >> >>>> > located in >> >>>> > the dynamic library link vtkCommon.dll" !!!!! >> >>>> > >> >>>> > I run on WinXP SP3, visual studio 9 2008 and the latest version of >> >>>> > Paraview >> >>>> > and Qt >> >>>> > >> >>>> > as I mentioned I added all the paths to all this dlls to the user >> >>>> > environment variable but somehow the system does not see this >> >>>> > dlls!!! >> >>>> > and >> >>>> > it will be really inconvenient to add all this dlls every time you >> >>>> > write a >> >>>> > software and want to run it! >> >>>> > >> >>>> > any help is really appreciated! >> >>>> > >> >>>> > best >> >>>> > ~Sam >> >>>> > >> >>>> > >> >>>> > On Mon, May 10, 2010 at 12:31 PM, Utkarsh Ayachit >> >>>> > <utkarsh.ayac...@kitware.com> wrote: >> >>>> >> >> >>>> >> 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 Mon, May 10, 2010 at 12:26 PM, A M <ars...@uga.edu> wrote: >> >>>> >> > thanks Utkarsh >> >>>> >> > >> >>>> >> > The page you suggested cleared some stuff for me! >> >>>> >> > As David suggested I tried to look at the examples under >> >>>> >> > Examples\CustomApplications directory in the paraview source. I >> >>>> >> > CMake'd >> >>>> >> > the >> >>>> >> > examples there such as Clone1&2 and Demo0&1 and tried to run >> >>>> >> > them >> >>>> >> > to see >> >>>> >> > how >> >>>> >> > they work (That would be a good working example to understand >> >>>> >> > the >> >>>> >> > process >> >>>> >> > better), the projects compiled just fine but when I tried to run >> >>>> >> > them I >> >>>> >> > got >> >>>> >> > the following two errors for Clone and Demo respectively: >> >>>> >> > "pqapplicationcomponents.dll was not found, re-installing the >> >>>> >> > application >> >>>> >> > may fix this problem" >> >>>> >> > "pqCore.dll was not found, re-installing the application may fix >> >>>> >> > this >> >>>> >> > problem" >> >>>> >> > >> >>>> >> > anyone has any idea what I did wrong here! what are these two >> >>>> >> > dll >> >>>> >> > files? >> >>>> >> > >> >>>> >> > best >> >>>> >> > ~sam >> >>>> >> > >> >>>> >> > On Sun, May 9, 2010 at 11:02 PM, Utkarsh Ayachit >> >>>> >> > <utkarsh.ayac...@kitware.com> wrote: >> >>>> >> >> >> >>>> >> >> 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 merged from >> >>>> >> >> > Utkarsh's >> >>>> >> >> > bleeding edge repository mentioned in the paper, into the >> >>>> >> >> > ParaView >> >>>> >> >> > development branch, and then into the 3.8 release of >> >>>> >> >> > ParaView. >> >>>> >> >> > >> >>>> >> >> > So just follow instructions from www.paraview.org to get the >> >>>> >> >> > ParaView >> >>>> >> >> > source, either 3.8 or current developement from git and use >> >>>> >> >> > that >> >>>> >> >> > make >> >>>> >> >> > your own custom applications. >> >>>> >> >> > >> >>>> >> >> > In particular, the sample applications mentioned in the >> >>>> >> >> > presentation >> >>>> >> >> > that accompanied the paper are under the >> >>>> >> >> > Examples/Applications >> >>>> >> >> > directory. >> >>>> >> >> > >> >>>> >> >> > David E DeMarle >> >>>> >> >> > Kitware, Inc. >> >>>> >> >> > R&D Engineer >> >>>> >> >> > 28 Corporate Drive >> >>>> >> >> > Clifton Park, NY 12065-8662 >> >>>> >> >> > Phone: 518-371-3971 x109 >> >>>> >> >> > >> >>>> >> >> > >> >>>> >> >> > >> >>>> >> >> > On Sun, May 9, 2010 at 9:33 PM, A M <ars...@uga.edu> wrote: >> >>>> >> >> >> >> >>>> >> >> >> Hi >> >>>> >> >> >> I sent the following email to Paraview mailing list and >> >>>> >> >> >> someone >> >>>> >> >> >> just >> >>>> >> >> >> answered back the the github was obsolete!! can you please >> >>>> >> >> >> guid >> >>>> >> >> >> me >> >>>> >> >> >> in a >> >>>> >> >> >> right direction to download the correct source for the >> >>>> >> >> >> purpose >> >>>> >> >> >> of >> >>>> >> >> >> Customizing Paraview please. is there any tutorial I can >> >>>> >> >> >> look >> >>>> >> >> >> in to? >> >>>> >> >> >> >> >>>> >> >> >> best >> >>>> >> >> >> Sam >> >>>> >> >> >> >> >>>> >> >> >> 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 and says the "The branding code is on >> >>>> >> >> >> the >> >>>> >> >> >> Branding >> >>>> >> >> >> branch, and a new reference application, called >> >>>> >> >> >> paraview_revamed will be found in Applications/Client2 that >> >>>> >> >> >> is >> >>>> >> >> >> what >> >>>> >> >> >> I >> >>>> >> >> >> can >> >>>> >> >> >> NOT find. where is this branding branch exactly and how can >> >>>> >> >> >> I >> >>>> >> >> >> download >> >>>> >> >> >> the >> >>>> >> >> >> rest of what he is talking about? Does anyone knows? >> >>>> >> >> >> >> >>>> >> >> >> I looked at http://github.com/utkarshayachit/ParaView the >> >>>> >> >> >> ParaView >> >>>> >> >> >> code is >> >>>> >> >> >> there but I didn't see anything called branding branch! Can >> >>>> >> >> >> anyone >> >>>> >> >> >> help >> >>>> >> >> >> me >> >>>> >> >> >> please! >> >>>> >> >> >> >> >>>> >> >> >> Best! >> >>>> >> >> >> ~sam >> >>>> >> >> >> >> >>>> >> >> >> >> >>>> >> >> >> >> >>>> >> >> >> >> >>>> >> >> > >> >>>> >> > >> >>>> >> > >> >>>> >> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> _______________________________________________ >> >>>> 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 >> >>> >> >> >> >> >> > >> > >> > > > > > _______________________________________________ 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