<div dir="ltr">It does, but it does not blow away any CMake cached variables from CMakeCache.txt, which is where the OpenGL libs and header locations are stored.<br><br><div><br><div class="gmail_quote">On Fri, Sep 5, 2008 at 11:11 AM, Labitt, Bruce <span dir="ltr"><<a href="mailto:labittb1@tycoelectronics.com">labittb1@tycoelectronics.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I was wondering about make clean. Doesn't that clean up stuff that vtk<br>
may have scattered thru my disk, libraries etc? I am definitely blowing<br>
away VTK-build.<br>
<div class="Ih2E3d"><br>
-Bruce<br>
<br>
-----Original Message-----<br>
From: Mike Jackson [mailto:<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>]<br>
</div><div><div></div><div class="Wj3C7c">Sent: Friday, September 05, 2008 11:04 AM<br>
To: Labitt, Bruce<br>
Cc: <a href="mailto:vtkusers@vtk.org">vtkusers@vtk.org</a><br>
Subject: Re: [vtkusers] Getting Started Questions<br>
<br>
The surest way to get a complete rebuild is to just blow away<br>
everything in the VTK-Build directory. Rerun ccmake setting all your<br>
custom selections that you want. The rebuild.<br>
<br>
You can try running cmake ../VTK from the VTK-Build directory and see<br>
if the newer ATI stuff is picked up. I am not sure how to tell that<br>
though. I would just blow away and start over. The build is relatively<br>
quick on a newer machine. 15 Minutes or so.<br>
<br>
---<br>
Mike Jackson - Principal Software Engineer<br>
<a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
<br>
<br>
On Sep 5, 2008, at 10:56 AM, Labitt, Bruce wrote:<br>
<br>
> I originally used ccmake and set "t" for the advanced view. I did not<br>
> use RPATH originally. In ccmake I set enabling python.<br>
><br>
> BUILD_TESTING is on. I just did a make test and found that most tests<br>
> failed. Umm, 916 out of 952 tests failed!<br>
><br>
> I just realized that I built vtk BEFORE I installed the ATI3D drivers.<br>
> That means I did not have "opengl" stuff installed. So, do I need to<br>
> rebuild vtk? I presume yes.<br>
><br>
> If I need to rebuild, then what do I do?<br>
><br>
> make clean ? to uninstall everything<br>
><br>
> Then delete the contents of /VTK-build<br>
> and execute<br>
> [VTK-build]$ env CC=/usr/bin/gcc CXX=/usr/bin/g++ ccmake ../VTK<br>
><br>
> This is because I want to do a out-of-source build.<br>
><br>
> Does that sound right? /VTK has the original files, and /VTKData the<br>
> data files.<br>
><br>
> Directory Structure<br>
> /home/me<br>
> /home/me/VTK ==> unmolested extracted files<br>
> /home/me/VTK-build ==> where I want stuff to be built<br>
> /home/me/VTKData ==> unmolested data files<br>
><br>
> Thanks<br>
> -Bruce<br>
><br>
> -----Original Message-----<br>
> From: Mike Jackson [mailto:<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>]<br>
> Sent: Friday, September 05, 2008 10:02 AM<br>
> To: Labitt, Bruce<br>
> Cc: <a href="mailto:vtkusers@vtk.org">vtkusers@vtk.org</a><br>
> Subject: Re: [vtkusers] Getting Started Questions<br>
><br>
> Couple ideas, but they may be way off for Linux.<br>
> First, use "ccmake" to run the "gui" version of cmake. After that<br>
> launches press the "t" key to get the advanced view. Scroll down the<br>
> list and look for VTK_USE_RPATH (I think that is it) and turn that ON.<br>
> This allows running VTK apps from the build directory but will stop<br>
> any type of actual "install" of vtk. This may solve the library<br>
> loading issues.<br>
><br>
> Still in ccmake, there is an option to "BUILD_TESTING". Turn this<br>
> on or make sure it was ON. Type "c" to configure again. Type "g" to<br>
> generate new makefiles and exit ccmake.<br>
> Recompile vtk. If you have a multi-core/multi-processor system use<br>
> "make -j2" to help speed up the recompile.<br>
> After the compilation reaches 100% you can do a "make test" which<br>
> will run all the tests and report any errors. Simply watch the output<br>
> for any tests that fail. If they all pass then you have a good build.<br>
><br>
> Hope some of that helps<br>
> -----<br>
> Mike<br>
> <a href="http://www.bluequartz.net" target="_blank">www.bluequartz.net</a><br>
><br>
> On Sep 5, 2008, at 9:54 AM, Labitt, Bruce wrote:<br>
><br>
>> Thanks Mike.<br>
>><br>
>> Believe me, I'm far from a guru myself - that is why I am "here"<br>
>> asking<br>
>> questions. Instead of using LD_LIBRARY_PATH, shouldn't I just use<br>
>> ldconfig for the new directory of libraries? I would have thought<br>
>> the<br>
>> build process would have done this already..<br>
>><br>
>> Yes, compile did reach 100%. Is there a log file showing that<br>
>> everything passes?<br>
>><br>
>> -----Original Message-----<br>
>> From: Mike Jackson [mailto:<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>]<br>
>> Sent: Friday, September 05, 2008 9:18 AM<br>
>> To: Labitt, Bruce<br>
>> Cc: <a href="mailto:vtkusers@vtk.org">vtkusers@vtk.org</a><br>
>> Subject: Re: [vtkusers] Getting Started Questions<br>
>><br>
>> I am not a linux guru but it looks like your LD_LIBRARAY_PATH may<br>
>> need<br>
>> to include the VTK-build/bin directory.<br>
>><br>
>> Also, when you compiled vtk, did the compile reach 100% ?? That would<br>
>> indicate a successful compile.<br>
>><br>
>> Mike<br>
>><br>
>> On Sep 5, 2008, at 8:57 AM, Labitt, Bruce wrote:<br>
>><br>
>>> I'm trying to get started with vtk. I have downloaded vtk5.2. I<br>
>>> used<br>
>>> cmake 2.6 to build vtk on a RHEL5.2 clone. How can I tell if the<br>
>>> build<br>
>>> is really successful? Can I examine an output file? Is there a<br>
>>> test<br>
>>> suite I can run?<br>
>>><br>
>>> I have built vtk out of place into a VTK-build directory. Some of<br>
>>> the<br>
>>> files in the VTK-build/bin directory do not run, for instance,<br>
>>> when I<br>
>>> run<br>
>>> [ bin]$./GraphicsCxxTests the result is<br>
>>><br>
>>> ./GraphicsCxxTests: error while loading shared libraries:<br>
>>> libvtkRendering.so.5.2: cannot open shared object file: No such file<br>
>>> or<br>
>>> directory<br>
>>><br>
>>> libvtkRendering.so.5.2 is in the current directory bin<br>
>>><br>
>>> Other files do run, like Medical1, and Cone6.<br>
>>><br>
>>> I attempted to compile in python support. I cannot tell if this was<br>
>>> done properly however. If I type<br>
>>> [ VTK-build/bin] $ vtkpython<br>
>>><br>
>>> I get<br>
>>> vtk version 5.0.4, vtk source rather than the expected 5.2. Is<br>
>>> this<br>
>>> correct?<br>
>>><br>
>>> If I type [ VTK-build/bin]$ ./vtkpython I get<br>
>>><br>
>>> ./vtkpython: error while loading shared libraries: libvtkViews.so.<br>
>>> 5.2:<br>
>>> cannot open shared object file: No such file or directory.<br>
>>><br>
>>> There is a libvtkViews.so.5.2 in the directory...<br>
>>><br>
>>> Any tips or help would be greatly appreciated.<br>
>>><br>
>>> Thanks,<br>
>>> Bruce<br>
><br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
This is the private VTK discussion list.<br>
Please keep messages on-topic. Check the FAQ at: <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
</div></div></blockquote></div><br></div></div>