The way it works is like this:
* The part of libtool that you include in your project, provided that
you don't need its loadable module support, is an Autoconf macro that
goes into aclocal.m4 or whatever, just like any other, and a giant
shell script that needs some Autoconf substitutions that's called
ltmain.sh. Both of these are covered under the Autoconf license, which
means you can include them in your package under your existing
distribution terms with no licensing problems.
There's a tool called libtoolize that basically does this for you, updating
ltmain.sh (aclocal.m4 too?) from the currently installed libtool.
Cheers, Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r !y?(-)
------END GEEK CODE BLOCK------
_______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
