On Tue, Jul 01, 2008 at 10:32:53AM -0400, Bob Rossi wrote: > On Mon, Jun 30, 2008 at 05:36:48PM -0400, Bob Rossi wrote: > > On Tue, Jan 08, 2008 at 09:53:24PM +0100, Ralf Wildenhues wrote: > > > Hello Bob, > > > > > > * Bob Rossi wrote on Tue, Jan 08, 2008 at 08:18:56PM CET: > > > > > > > > plugindir = $(libdir)/plugins > > > > plugin_LTLIBRARIES = > > > > plugin_LTLIBRARIES += libfoo.la > > > > libfoo_la_SOURCES = foo.cc > > > > libfoo_la_LDFLAGS = "-no-undefined" > > > > > > > > Now when I do 'make install' with --prefix=install I see this, > > > > on linux, I get install/lib/plugins/libfoo.so > > > > on windows, I get install/lib/bin/libfoo-0.dll > > > > > > > > Any idea why the dll isn't going into the plugins dir and why > > > > it is going into lib/bin? > > > > > > I'd say that's a bug. Thanks for the report. > > > > Here there been any progress on this issue? Are there any workarounds I > > could use? > > Also, if I use > AM_LDFLAGS = "-no-undefined -module -avoid-version" > or > AM_LDFLAGS = "-no-undefined -avoid-version" > instead of just > AM_LDFLAGS = "-no-undefined" > > Then the dll doesn't get built at all. Am I doing something silly?
Sorry to spam, I did see this in the build output, libtool: link: warning: undefined symbols not allowed in i686-pc-mingw32 shared libraries Does that explain why I don't have any dll's in the above case? Thanks, Bob Rossi _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
