[vtkusers] Getting Started Questions

[Mike Jackson]

make clean only cleans up the build directory.

Mike

On Sep 5, 2008, at 11:11 AM, Labitt, Bruce wrote:

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

  _________________________________________________
| Mike Jackson - Principal Software Engineer      |
| BlueQuartz Software                             |
| mike.jackson at bluequartz.net                     |
| www.bluequartz.net                              |
---------------------------------------------------