[vtk-developers] Re: vtkpython_pyc target dependencies - followup

[Utkarsh Ayachit]

Phew! Am I glad that the problem is resolved :).

I am not sure why the dlls are installed in lib directory. Perhaps 
someone on list might know the reason behind that.

Utkarsh

Andrew Maclean wrote:

>Guess what ... I found the problem (thanks to your comments below). I think
>it was mismatched dlls. I suspect that it was picking up an older dll.
>
>I use the INSTALL project to install all the VTK stuff into c:\Program
>Files\VTK. I think it was picking up the old dlls in these directories (15
>July) thus causing a conflict. I just renamed the bin and lib directories in
>c:\Program Files\VTK and the install worked OK. 
>
>Actually ... while you are looking at Python - why do the dll's end up in
>the lib directory and not the bin directory when doing the install?
>I.e. they are ending up in C:\Program Files\VTK\lib\vtk; and not in
>C:\Program Files\VTK\bin with the rest of the dlls.
>
>
>Thanks again, Utkarsh - you put me on the right track. 
>Maybe I am then only person who uses INSTALL!
>
>
>For your information:
>
>1) Project dependencies are OK - it ultimately depends upon vtkCommon.
>
>2) The first command "import vtk" works OK.
>I have in my path: PATH=C:\Python24\;C:\Tcl\bin;C:\Perl\bin\; C:\Program
>Files\VTK\bin;C:\vtk\build\VTKAndrew-build\bin\release;C:\Program
>Files\ParaView\bin;...
>
>And also defined: 
>
>PYTHONPATH=C:\Program Files\VTK\bin;C:\Program
>Files\VTK\lib\vtk;C:\vtk\VTK\Wrapping\Python;C:\vtk\VTK\Wrapping\Python\vtk;
>C:\vtk\build\VTKAndrew-build\bin\release
>TCLLIBPATH="C:/Program Files/VTK/lib/vtk/tcl"  C:/vtk/VTKAndrew/Wrapping/Tcl
>
>
>Andrew
>
>
>
>
>-----Original Message-----
>From: Utkarsh Ayachit [mailto:utkarsh.ayachit at gmail.com] 
>Sent: Friday, 29 July 2005 16:13
>To: Andrew Maclean
>Subject: Re: [vtk-developers] Re: vtkpython_pyc target dependencies -
>followup
>
>I am equally puzzled.
>Can you give me the new error message. It should have changed from before.
>Also, just to verify that the dependencies are fine..could you
>right-click on one of the testing projects (say GraphicsPythonTests)
>and check "Project Dependencies". Keep following the dependencies up
>to ensure that the test eventually depends on vtkCommon (which would
>ensure proper build order.) But then, that's not the problem...if I
>understand you correctly,
>right now vtk is built fine except the python tests. So, you can run
>vtkpython and all's fine. But when you try to build the tests, they
>fail.
>
>you can try one more thing.
>* go to a random dir say c:\tmp
>* run python.exe
>  
>
>>>import vtk
>>>      
>>>
>-- this will typically raise an error....unless you have the VTK dir
>in your environment PATH. If it raises an error then do the following:
>  
>
>>>import sys
>>>sys.path.append("<absolute path to VTKBinDir/Utilities/vtkTclTest2Py>")
>>>sys.path.append("<absolute path to VTKBinDir/bin/Debug>") (or
>>>      
>>>
>bin/Release as the case may be)
>  
>
>>>import vtk
>>>      
>>>
>This import should succeed. 
>
>if the import fails ...try one more thing.
>  
>
>>>sys.path.append("<absolute path to VTKBinDir/Wrapping/Python")
>>>import vtk
>>>      
>>>
>if this import succeeds, then we know the problem....I have not added
>all the required paths while trying to convert the tests and although
>it would still remain a mystery as to why it succeeds on all the
>windows configurations I;ve tried, atleast we'll know why it fails for
>you--- and should be an easy fix.
>Let me know which "import vtk", if any succeeds.
>
>Utkarsh
>
>
>
>Utkarsh.
>
>On 7/28/05, Andrew Maclean <a.maclean at cas.edu.au> wrote:
>  
>
>>After removing all the source files and all the build files and getting
>>    
>>
>the
>  
>
>>source from the CVS again the same problem occurs.
>>
>>I am really puzzled.
>>
>>
>>Andrew
>>
>>-----Original Message-----
>>From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>>Sent: Friday, 29 July 2005 05:36
>>Cc: Andrew Maclean; 'vtk-developers'
>>Subject: Re: [vtk-developers] Re: vtkpython_pyc target dependencies -
>>followup
>>
>>Andrew,
>>
>>It still beats me why it's failing for you. I wasn't able to reproduce
>>it - nor do any of the dashboards. I tried to reproduce your build, but
>>to no avail.
>>
>>The error is cleary while converting the tcl testing scripts to python
>>tests. The conversion script yells for "-f" option when it was not able
>>to load the vtk module (which would indeed happen if vtkCommon.dll was
>>not found). Which could happen while  attempting to convert the test
>>before the compilation of all the kits(common, rendering etc..).  That
>>being the case, the conversion should fail for the first attempt to
>>convert. On closer inspection, we note that the all errors you indicated
>>were for the last test in the sequence of tests to be converted -
>>implying all the previous tests were converted - implying that vtk
>>python module is loadable - and that's curious!
>>
>>Also, with the current CVS version(after 7/26/05) the error should have
>>changed since the tests are no longer converted individually (as on
>>7/25/05) but all the tests for a kit are converted in one shot.
>>
>>Have you tried rebulding everything? Since I was changing the python_pyc
>>and testing dependencies as I was working on it, may be your build has
>>ended up in some weird state (yes, I am out of options!).
>>
>>Utkarsh
>>
>>Utkarsh Ayachit wrote:
>>
>>    
>>
>>>Andrew,
>>>
>>>I am having a hard time reproducing this problem.
>>>Can you email me your CMakeCache.txt (in the build dir)?
>>>
>>>Utkarsh
>>>
>>>Andrew Maclean wrote:
>>>
>>>      
>>>
>>>>It definitely is vtkCommon.dll missing in the python tests.
>>>>As of UTC 2005 July 27 02:00.
>>>>
>>>>Regards
>>>>Andrew
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>_______________________________________________
>>>vtk-developers mailing list
>>>vtk-developers at vtk.org
>>>http://www.vtk.org/mailman/listinfo/vtk-developers
>>>
>>>      
>>>
>>
>>
>>    
>>
>
>
>
>
>  
>