vtkLocal in 15 Easy Steps (was RE: [vtkusers] VTK 4.0 Local?)
Sebastien BARRE
sebastien.barre at kitware.com
Wed Dec 19 13:10:36 EST 2001
At 12/19/2001 12:11 PM, Volpe, Christopher R (CRD) wrote:
> > - your approach will work for you. But what if your team
> > share the same VTK
> > build dir and some other people want to build their very own
> > local stuff ?
>
>We don't share source trees here. If you do, you have the same problem you'd
>have if each team member added his own not-yet-fully-developed classes to,
>say, vtkCommon.
Why would they ? I mean, why vtkCommon ? These classes would go in their
local stuff (vtkLocal in your approach).
>Whatever works, as long as I can do all my local stuff in the same vtk.dsw
>workspace.
No, you won't.
>I want all the
>browse information available when I'm working with my local classes. I
>also like being able to simply do "package require vtk"
You won't too, you wil have some kind of:
package require myvtklocal
--
Sebastien Barre
More information about the vtkusers
mailing list