To set the PATH when debugging from the IDE:<div><br></div><div>1. Right click the project and select Properties</div><div>2. In the tree view on the left select Debugging</div><div>3. In the main panel there will be an entry called 'Environment'</div>
<div>4. Set the Path by entering something like:</div><div><br></div><div>PATH=C:\Path\To\Something;%PATH%<br><div><br><div class="gmail_quote">On Tue, May 11, 2010 at 12:28 PM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Well, unfortunately, the DLL mess is a Windows OS thing. I am not a<br>
regular Windows developer so I cannot tell you exactly how to access<br>
that option, but Visual Studio does have an option somewhere that<br>
allows you to specify the environment in which the application is<br>
running. There you can set the PATH to include the ParaView bin/debug<br>
(or bin/release as the case maybe) and Qt dirs.<br>
<br>
You might want to download dependency walker<br>
(<a href="http://www.dependencywalker.com/" target="_blank">http://www.dependencywalker.com/</a>), a handy utility to determine<br>
exactly what dlls are being used/not found etc. Use this to ensure<br>
that correct versions of the dlls are being imported.<br>
<br>
I'd refrain from copying over dlls, this often leads to user-related<br>
errors down the line.<br>
<br>
As far as the missing symbol error goes, it's possible your program is<br>
accidentally bringing in a mismatched vtkCommon dll. Do you have other<br>
VTK / ParaView builds in your PATH? Use the dependency walker to<br>
ensure that it's using the correct vtkCOmmon (and other) dlls.<br>
<br>
Hope that helps.<br>
<font color="#888888"><br>
Utkarsh<br>
</font><div><div></div><div class="h5"><br>
<br>
On Tue, May 11, 2010 at 3:17 PM, A M <<a href="mailto:arsham@uga.edu">arsham@uga.edu</a>> wrote:<br>
><br>
> As you suggested, I added the dll path (ParaView-3.8.0-bin\bin\Debug) to the<br>
> environment variable as well as the Qt path, however when I ran the .exe<br>
> file again I got the same error, so I added the dll files manually to the<br>
> same directory as the .exe file, at first was asking about some Paraview<br>
> dlls and the some Qt dlls (I have both of this added to the use path<br>
> enviroment variable!) and then asked form some vtk dlls, the last error<br>
> which I can not get passed of is asking for vtkCommon.dll, I added the dll<br>
> to the directory and I got this:<br>
><br>
> " the procedure entry point<br>
> ?ComputePointForExtent@vtkStructuredData@@SAQAH0@Z could not be located in<br>
> the dynamic library link vtkCommon.dll" !!!!!<br>
><br>
> I run on WinXP SP3, visual studio 9 2008 and the latest version of Paraview<br>
> and Qt<br>
><br>
> as I mentioned I added all the paths to all this dlls to the user<br>
> environment variable but somehow the system does not see this dlls!!! and<br>
> it will be really inconvenient to add all this dlls every time you write a<br>
> software and want to run it!<br>
><br>
> any help is really appreciated!<br>
><br>
> best<br>
> ~Sam<br>
><br>
><br>
> On Mon, May 10, 2010 at 12:31 PM, Utkarsh Ayachit<br>
> <<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>> wrote:<br>
>><br>
>> When you are running on windows, windows expects that all the dlls are<br>
>> in PATH (or the same location as the exe). You may want to start the<br>
>> clone executable from a terminal ensuring that you set the PATH<br>
>> environment variable correctly to point to the dlls under the ParaView<br>
>> build dir.<br>
>><br>
>> Utkarsh<br>
>><br>
>> On Mon, May 10, 2010 at 12:26 PM, A M <<a href="mailto:arsham@uga.edu">arsham@uga.edu</a>> wrote:<br>
>> > thanks Utkarsh<br>
>> ><br>
>> > The page you suggested cleared some stuff for me!<br>
>> > As David suggested I tried to look at the examples under<br>
>> > Examples\CustomApplications directory in the paraview source. I CMake'd<br>
>> > the<br>
>> > examples there such as Clone1&2 and Demo0&1 and tried to run them to see<br>
>> > how<br>
>> > they work (That would be a good working example to understand the<br>
>> > process<br>
>> > better), the projects compiled just fine but when I tried to run them I<br>
>> > got<br>
>> > the following two errors for Clone and Demo respectively:<br>
>> > "pqapplicationcomponents.dll was not found, re-installing the<br>
>> > application<br>
>> > may fix this problem"<br>
>> > "pqCore.dll was not found, re-installing the application may fix this<br>
>> > problem"<br>
>> ><br>
>> > anyone has any idea what I did wrong here! what are these two dll files?<br>
>> ><br>
>> > best<br>
>> > ~sam<br>
>> ><br>
>> > On Sun, May 9, 2010 at 11:02 PM, Utkarsh Ayachit<br>
>> > <<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>> wrote:<br>
>> >><br>
>> >> You might also want to refer to the following wiki page details on the<br>
>> >> custom application components:<br>
>> >> <a href="http://paraview.org/Wiki/Writing_Custom_Applications" target="_blank">http://paraview.org/Wiki/Writing_Custom_Applications</a><br>
>> >><br>
>> >> Utkarsh<br>
>> >><br>
>> >> On Sun, May 9, 2010 at 9:48 PM, David E DeMarle<br>
>> >> <<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>> wrote:<br>
>> >> > Since that time, the branding infrastructure has merged from<br>
>> >> > Utkarsh's<br>
>> >> > bleeding edge repository mentioned in the paper, into the ParaView<br>
>> >> > development branch, and then into the 3.8 release of ParaView.<br>
>> >> ><br>
>> >> > So just follow instructions from <a href="http://www.paraview.org" target="_blank">www.paraview.org</a> to get the ParaView<br>
>> >> > source, either 3.8 or current developement from git and use that make<br>
>> >> > your own custom applications.<br>
>> >> ><br>
>> >> > In particular, the sample applications mentioned in the presentation<br>
>> >> > that accompanied the paper are under the Examples/Applications<br>
>> >> > directory.<br>
>> >> ><br>
>> >> > David E DeMarle<br>
>> >> > Kitware, Inc.<br>
>> >> > R&D Engineer<br>
>> >> > 28 Corporate Drive<br>
>> >> > Clifton Park, NY 12065-8662<br>
>> >> > Phone: 518-371-3971 x109<br>
>> >> ><br>
>> >> ><br>
>> >> ><br>
>> >> > On Sun, May 9, 2010 at 9:33 PM, A M <<a href="mailto:arsham@uga.edu">arsham@uga.edu</a>> wrote:<br>
>> >> >><br>
>> >> >> Hi<br>
>> >> >> I sent the following email to Paraview mailing list and someone just<br>
>> >> >> answered back the the github was obsolete!! can you please guid me<br>
>> >> >> in a<br>
>> >> >> right direction to download the correct source for the purpose of<br>
>> >> >> Customizing Paraview please. is there any tutorial I can look in to?<br>
>> >> >><br>
>> >> >> best<br>
>> >> >> Sam<br>
>> >> >><br>
>> >> >> Hi!<br>
>> >> >><br>
>> >> >> So I am a little confused! I read a paper by Utkarsh A. Ayachit and<br>
>> >> >> in<br>
>> >> >> this<br>
>> >> >> paper he mentioned to clone the repository at<br>
>> >> >> git://<a href="http://github.com/utkarshayachit/ParaView.git" target="_blank">github.com/utkarshayachit/ParaView.git</a> to obtain the modified<br>
>> >> >> ParaView<br>
>> >> >> source, up to here it is just fine, I can clone the directory just<br>
>> >> >> fine.<br>
>> >> >> Then he goes on and and says the "The branding code is on the<br>
>> >> >> Branding<br>
>> >> >> branch, and a new reference application, called<br>
>> >> >> paraview_revamed will be found in Applications/Client2 that is what<br>
>> >> >> I<br>
>> >> >> can<br>
>> >> >> NOT find. where is this branding branch exactly and how can I<br>
>> >> >> download<br>
>> >> >> the<br>
>> >> >> rest of what he is talking about? Does anyone knows?<br>
>> >> >><br>
>> >> >> I looked at <a href="http://github.com/utkarshayachit/ParaView" target="_blank">http://github.com/utkarshayachit/ParaView</a> the ParaView<br>
>> >> >> code is<br>
>> >> >> there but I didn't see anything called branding branch! Can anyone<br>
>> >> >> help<br>
>> >> >> me<br>
>> >> >> please!<br>
>> >> >><br>
>> >> >> Best!<br>
>> >> >> ~sam<br>
>> >> >><br>
>> >> >><br>
>> >> >><br>
>> >> >><br>
>> >> ><br>
>> ><br>
>> ><br>
>> ><br>
><br>
><br>
><br>
><br>
</div></div><div><div></div><div class="h5">_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
</div></div></blockquote></div><br></div></div>