<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7232.77">
<TITLE>RE: [vtk-developers] extension wrangler</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>The dlopen technique was dissabled because it was proving to be unreliable. Some of VTK's dashboard tests were continually failing because VTK was being compiled against one OpenGL library (which happened to be static) and the dlopen was openening a shared object library elsewhere. Thus, it would look like the extension was loaded correctly, but the application would crash if you tried to use any of the functions.<BR>
<BR>
Ultimately we could not figure out a way to ensure that the dlopen tried to open the same library that was already being used. (The problem gets more compilicated when you compile on one machine and run on another.) If someone could solve this problem, then the dlopen method would work just fine.<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: vtk-developers-bounces+kmorel=sandia.gov@vtk.org on behalf of Jeff Lee<BR>
Sent: Tue 11/15/2005 12:31 PM<BR>
To: vtk-developers<BR>
Subject: [vtk-developers] extension wrangler<BR>
<BR>
Hi,<BR>
Does anyone know why the extension wrangler in vtk has the fallback<BR>
dlopen technique disabled? Is there some way this could be fixed for<BR>
systems without glxProcAddressARB functionality? Is the wrangler meant<BR>
to be a runtime wrangler, or just compile-time?<BR>
Regards,<BR>
Jeff<BR>
_______________________________________________<BR>
vtk-developers mailing list<BR>
vtk-developers@vtk.org<BR>
<A HREF="http://www.vtk.org/mailman/listinfo/vtk-developers">http://www.vtk.org/mailman/listinfo/vtk-developers</A><BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>