[vtkusers] Getting Started Questions

[Mike Jackson]

You need to add the directory where libavcodec.so to your  
LD_LIBRARY_PATH variable and then try rerunning the test.  
libavcodec.so was probably built without an rpath otherwise there  
wouldn't be a problem finding it.

Mike

On Sep 5, 2008, at 3:30 PM, Labitt, Bruce wrote:

> OK.  Ran the test
>
> $ ctest -V -I 20,20,
>
> error while loading shared libraries: libavcodec.so.51: cannot open
> shared object file: No such file or directory.
>
> libavcodec.so is in the directory that I told cmake where it was...
>
> It appear that my library links are not getting updated?  Do I need to
> edit ld.so.conf ?  isn't there a way to load or add a directory's  
> worth
> of libs to the system?
>
> -Bruce
>
> -----Original Message-----
> From: David E DeMarle [mailto:dave.demarle at kitware.com]
> Sent: Friday, September 05, 2008 3:10 PM
> To: David Cole
> Cc: Labitt, Bruce; vtkusers at vtk.org
> Subject: Re: [vtkusers] Getting Started Questions
>
> The detailed test results end up in being placed in
> Testing/Temporary/LastTest.log. If you add "-V" to the ctest command,
> the same information will be shown on the screen.
>
> As Mike suggested, you should look at that and figure out "why" the
> tests are failing.
>
> ctest -I N,N,
> will run just the N'th test.
>
> cheers,
> Dave DeMarle
>
>
> On Fri, Sep 5, 2008 at 3:03 PM, David Cole <david.cole at kitware.com>
> wrote:
>> ctest -R "^TestName$"
>> in the build directory will run just tests that match the regular
> expression
>> "^TestName$"
>>
>> On Fri, Sep 5, 2008 at 2:53 PM, Labitt, Bruce
> <labittb1 at tycoelectronics.com>
>> wrote:
>>>
>>> I just tried your suggestion.  We are getting a little closer.  Now
> 7%
>>> of the tests pass vs 4% before.
>>>
>>> The first 19 tests pass, then it gets a bit patchy.  I notice that
> lots
>>> of python related tests fail.
>>>
>>> -Bruce
>>>
>>> -----Original Message-----
>>> From: Mike Jackson [mailto:mike.jackson at bluequartz.net]
>>> Sent: Friday, September 05, 2008 2:35 PM
>>> To: Labitt, Bruce
>>> Cc: vtkusers at vtk.org
>>> Subject: Re: [vtkusers] Getting Started Questions
>>>
>>> Someone else can chime in here but I think there is a way to just  
>>> run
>>> one test. What you need to do is run one test that fails and figure
>>> out _why_ it failed. Did it fail because it couldn't find the
>>> libraries? or did it fail because OpenGL or the Window Manager  
>>> mucked
>>> things up?
>>>
>>> Try this?
>>>
>>> in your terminal (assuming bash) "export LD_LIBRARY_PATH=
>>> $LD_LIBRARY_PATH:/home/me/VTK-build/bin"
>>>
>>> and then try "make test" again.
>>>
>>> If everything goes just fine, then "make install" will install
>>> everything into the "CMAKE_INSTALL_PREFIX" location which is  
>>> probably
> /
>>> usr/local. If you want to "sandbox" the installation change the
>>> "CMAKE_INSTALL_PREFIX" to /usr/local/vtk-5.2 and build again.
>>>
>>> Mike
>>>
>>> On Sep 5, 2008, at 2:18 PM, Labitt, Bruce wrote:
>>>
>>>> I just did everything all over again.  It appeared that make
>>>> completed.
>>>> [100%] Built target VTKExamplesTarget is the last line.
>>>>
>>>> However, make test results in 4% of tests passing - all others
> fail.
>>>> This is the same as before.  I did not use RPATH.
>>>>
>>>> I'm trying again - maybe I messed something up.  I started with a
>>>> blank
>>>> VTK-build directory again.
>>>>
>>>> If [VTK-build] $ make        completed, then
>>>> [VTK-build] $ make test      should work if all is good?
>>>>
>>>> If make test is good then I do sudo make install, yes?
>>>>
>>>> -Bruce
>>>>
>>>> -----Original Message-----
>>>> From: David E DeMarle [mailto:dave.demarle at kitware.com]
>>>> Sent: Friday, September 05, 2008 11:25 AM
>>>> To: Labitt, Bruce
>>>> Cc: Mike Jackson; vtkusers at vtk.org
>>>> Subject: Re: [vtkusers] Getting Started Questions
>>>>
>>>> And unless you did a make install the only thing that configuring
> and
>>>> building vtk would change is the build directory.
>>>>
>>>> On Fri, Sep 5, 2008 at 11:11 AM, Labitt, Bruce
>>>> <labittb1 at tycoelectronics.com> 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
>>>>>>
>>>>>
>>>