Thanks for all of the input.  When it comes to this opengl stuff I  
have always been a bit in the dark about what is going on when things  
are compiled, so I just tinker around and see what happens.   
Regardless, the changes that I made seem to have a good effect on how  
things are running in analysis.  The redraw rate is still a bit slow  
and "laggy" (for lack of a better way to describe it), but when I am  
scrolling through menus things are much faster.  For example, when  
the assignment window is opened and you can select the atoms for  
assignment, the time to scroll to different residues is much faster.   
Before, there would be a 2-3 second delay between mouse clicks and  
actual scrolling.  Now it is < 1 second.  From my use it appears that  
the overall responsiveness of analysis is much better.

With all of the comments listed here, I would presume that it is not  
due to the OpenGL changes made, but rather to the optimized C code  
flags that I inserted.  Who knows....anyway, thanks for all of the  
insight into how OpenGL/Mesa/Glut work with analysis.

-J

On Mar 29, 2007, at 2:39 AM, Brian Smith wrote:

> I think there's a bit of confusion between what's required to  
> compile and what to run an OpenGL program. The gl.h file is only  
> required at compile time, defines various functions and constants,  
> and will be largely functionally similar between different versions  
> of OpenGL or Mesa (apart from perhaps some extensions that analysis  
> is unlikely to use).
>
> You also need the OpenGL libraries present at compile time for the  
> linker to link against, and with appropriate linker flags you can  
> direct the linker to pick a particular one at that time.
>
> However, analysis is typically compiled to use shared libraries and  
> so at run time it will usually link against  the system default  
> shared library that matches (on Macs that looks like the vendor- 
> supplied hardware accelerated library, which is probably the best  
> option). If you specifically want to use different OpenGL libraries  
> installed off the standard shared library search path then you will  
> need to get clever with the LD_LIBRARY_PATH environment variable or  
> equivalent.
>
> You can check which libraries are really being used by a program  
> using lsof, but if you're seeing the ATI vendor string on your Mac,  
> you know you're getting the system library, whether you compiled  
> against Mesa or not.
>
> -- 
> Dr. Brian O. Smith ---------------------- B Smith at bio gla ac uk
>           Division of Biochemistry & Molecular Biology,
>               Institute Biomedical & Life Sciences,
> Joseph Black Building, University of Glasgow, Glasgow G12 8QQ, UK.
> Tel: 0141 330 5167/6459/3089                    Fax: 0141 330 8640