"Braden N. McDaniel" <[EMAIL PROTECTED]> writes:
> 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.
[snip]
One way to solve the problem you describe can be found in several
widely used libraries, like gtk+, glib, the gnome libraries, etc.
The solution involves configure building a [libname]-config.sh shell
script, containing full information about the other libraries your
library depends on (like OpenGL), along with information on paths,
etc.
By making the autoconf detection macro you provide for checking the
presence of your library use this shell config script, you can then
"remember" the state of the system when your package was configured.
Check out the build system for one of the above mentioned libraries
(gtk+, glib, gnome-libs) or the library I'm working on (Coin) for
further information.
Hope that helps,
Morten
