[vtkusers] Re: [CMake] Can multiple builds of VTK share one install directory?

[Weiguang Guan]

Thanks, David. I will keep a common installation directory as long as 
switching between different VTK builds doesn't cause any side effect.

It's a good idea to manually clean up the installation directory before 
installing a build. But in my case, I want the common installlation 
directory to host not only VTK but other libs as well, and I must be very 
careful to remove ONLY vtk installation as there is no "make uninstall" 
for vtk.

Weiguang

On Thu, 5 Oct 2006, David Cole wrote:

> It can... but only because VTK's installation contains itself to its own make 
> install tree.
>
> And it may be wise to add a clean of the install directory in between, too...
> i.e.:
> cd Common_Install_Dir
> rm -rf *
> cd Build_B_Dir
> make install
>
> That way, you guarantee that there's nothing left in the Common_Install_Dir 
> from a previous install...
>
>
> HTH,
> David
>
>
> Weiguang Guan wrote:
>
>> Hello,
>> 
>> I need to keep multiple builds of VTK with different configurations. Can I 
>> direct their installations to the same location (shown as below) so that 
>> whenever my vtk-based app needs to be linked against Build B I can just "cd 
>> Build_B_Dir & make install"?
>>
>>        /--     Build A --\
>> VTK Source ---    Build B --- installation
>>        \--    Build C --/
>> 
>> Perhaps this question should go to cmake forum --- Can "make install" from 
>> one build directory completely overwrites what previously came from another 
>> build directory corresponding to the same source?
>> 
>> Weiguang
>> 
>