On Fri, Aug 8, 2008 at 3:43 PM, Roy Stogner <roy@...> wrote:
> On Fri, 8 Aug 2008, David Fuentes wrote:
>> on my 64bit machine,
>> the configure scripts are setting the vtk library path
>> to /usr/lib
>> what is the proper way to have the configure script default
>> to /usr/lib64
>> i guess i could also run
>> ./configure --with-vtk-lib=/usr/lib64
> That's the best way to do things at the moment.
> The VTK configuration is overwriting VTK_LIB in our aclocal.m4 file;
> should we be testing for an existing VTK_LIB environment variable
> first, and using that if it exists?
Yes, assuming that VTK_LIB is a standard environment variable set by
people who use VTK. I'm not familiar enough with VTK to know; when I
wrote that configure test I just picked something random.
We should probably at least change that configure variable to
LIBMESH_VTK_LIB and check to see if the user already has set something
for VTK_LIB (or whatever the standard one may be.)