On Sat, 11 Mar 2000, Matthew D. Langston wrote:
> Hi Braden,
>
> "Braden N. McDaniel" wrote:
> >
> > Suppose I've got a library and I want to install an autoconf macro on
> > the user's system so that if the user is developing a library
> > dependent on mine, s/he can use this macro to check for the presence
> > of my library. My library depends on OpenGL, so the macro I've
> > installed needs to check for OpenGL.
> >
> > [snip]
> >
> > Is there some way of addressing this problem other than having the
> > macro installed with autoconf? I really don't agree that an OpenGL
> > detection macro is too specialized to warrant such inclusion.
>
> You should be using Libtool to create your libraries, so that you can
> make use of Libtool's implicit handling of inter-library dependencies.
I do use libtool. Generally, however, an autoconf macro is needed so that
the user can specify the prefix under which a library has been installed
when a library is installed outside of the default search paths. I'm not
sure if this is necessary for libtool to find the library, but it is
needed for finding header files.
For OpenGL, however, this might not be an important issue. Your macro, at
least, assumes that OpenGL has been installed to a location the system
"knows" about. Perhaps that is a reasonable assumption in this case--I
don't really know.
--
Braden N. McDaniel
[EMAIL PROTECTED]
<URL:http://www.endoframe.com>
