[vtk-developers] Building relocatable libs

Steve Pieper pieper at bwh.harvard.edu
Wed Mar 10 20:04:54 EST 2004

Yes, I ran into this problem - now when I package up my program to 
distribute I substitute the attached file for the default pkgIndex.tcl 
file that has all the hardcoded paths in it.

Hope that helps,

ps. if there's a better solution, I'd love to hear it.

Chris Volpe wrote:

> I figure lots of people must have had a need to do this, so I’m sure 
> this is an easy question. I want to build VTK in a way that the result 
> can be placed on another machine, in an arbitrary location, and the user 
> of that machine will be able to run Wish script applications, As it 
> stands, the wrapping files in VTKBIN are full of absolute path names and 
> such, making it difficult to do a “package require vtk” unless you work 
> through all the absolute path names everywhere they exist and root them 
> all out. Is there a facility for doing this automatically?
> Thanks,
> **Chris**
> --
> Christopher R. Volpe, 
> Ph.D.                                                       
> Senior 
> Scientist                                                           
> Email: cvolpe at ara.com <mailto:cvolpe at ara.com>
> Applied Research Associates, Inc.                                Voice: 
> 919-582-3380
> 8540 Colonnade Center Dr., Ste 301                                   
> Fax: 919-878-3672
> Raleigh, NC 
> 27615                                                              Web: 
> www.ara.com <http://www.ara.com/>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: slicer-vtk-pkgIndex.tcl
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20040310/130c9c93/attachment.ksh>

More information about the vtk-developers mailing list