On Jul 10, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
> If I want to build a win32 DLL, I indicate this by putting
> AC_LIBTOOL_WIN32_DLL in my configure.in, right?
And promising to libtool that the library is self-contained, which you
do by adding -no-undefined to the command line that creates the
library.
> Does that macro arrange for the correct flags to be passed to
> libtool?
In a sense, it does, because the correct flags are no flags. Whether
a library is self-contained or not must be specified on a per-library
basis. So you have to add -no-undefined to the library's LDFLAGS, but
only if the library is self-contained.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
