[vtk-developers] copy Wrapping/Python, Wrapping/Tcl to VTKbin?

[Andy Cedilnik]

I agree with this. Similar question is about java build, which gets put
in VTKBin/java. This directory is not consistent with anything else. I
think after building VTK you should be able to delete source and all
build directories except bin and be able to run VTK. Maybe there should
be a lib directory, but it should most certainly be independent from
source tree.

			Andy

On Tue, 2002-07-23 at 10:26, David Gobbi wrote:
> Hi All,
> 
> But probably Prabhu and Seb the most, since they do most of
> the Wrapping/Python and Wrapping/Tcl maintenance.
> 
> What do people think of copying the python modules and
> tcl packages to VTKbin/bin (or perhaps VTKbin/python and
> VTKbin/tcl) as part of the standard 'make' process?
> 
> The reason is that VTKbin really should contain everything
> that is needed to run VTK, one VTK is built it would be
> nice if Python and Tcl did not have to refer to the source.
> 
> Another reason is that when Python scripts are run, a '.pyc'
> pre-compiled file is created in the VTK/Wrapping/Python directory.
> Because I share my source directory between several platforms
> this sometimes causes problems for me.