Re: DEFUN_DLD link rule

[John W. Eaton]

On 08/29/2013 11:33 PM, Michael Goffioul wrote:

> It's related, but not exactly the same. Under Windows, you only need to
> link against libraries you directly use in your code. You don't need to
> link against the dependencies of those libraries if you don't use
> symbols from those deps directly. I understand
> that --enable-link-all-dependencies includes all dependencies, but this
> is theoretically not needed under Windows.

I may have misunderstood the requirements when I added the
--enable-link-all-dependencies option.

> IIRC, I really only had problems with libgnu.la <http://libgnu.la>. I'm
> not sure --enable-link-all-dependencies would add it to the libs when
> linking liboctinterp, or the oct-files. Because MSVC does not support
> auto-exporting symbols, I had to add libgnu.la <http://libgnu.la>
> manually in libinterp/Makefile.am, src/Makefile.am
> and libinterp/dldfcn/config-module.awk.

Maybe I'm missing something, but I thought that libgnu.la is used as
a libtool convienience library for liboctave.la, so that all the
object files for that library are included in the liboctave shared
library and there is no separate libgnu shared library.  So I don't
understand why it would be necessary to link directly to libgnu.la at
all.  Why should libgnu.la be different from the other convenience
libraries that are used to construct the liboctave shared library?

jwe