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 +=
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 =
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 =
On Tue, Jan 08, 2008 at 11:29:15PM +0200, Tor Lillqvist wrote:
Shouldn't plug-in -type shared libraries be built with the -module
-avoid-version libtool flags? I think with those flags, such
libtool-built DLLs get installed in the libdir of the Makefile in
question, not libdir/../bin like
On Wed, 9 Jan 2008, Duft Markus wrote:
Bob Friesenhahn wrote:
On Tue, 8 Jan 2008, Ralf Wildenhues wrote:
General question before fixing this: on w32, should even plugins have
their DLLs go to $bindir?
Yes, i'd agree to this... ;o) If you try to load a library by yourself,
you will have to
On Wed, 9 Jan 2008, Bob Rossi wrote:
There should be no dependencies between plugins.
I don't know. That sentence goes a little to far really. When pcre is
built on windows, it creates two dlls. The first is the regex dll which
supports the POSIX regex functionality. The second is a C++
On Tue, Jan 08, 2008 at 11:29:15PM +0200, Tor Lillqvist wrote:
Shouldn't plug-in -type shared libraries be built with the -module
-avoid-version libtool flags? I think with those flags, such
libtool-built DLLs get installed in the libdir of the Makefile in
question, not libdir/../bin like
Bob Friesenhahn mailto:[EMAIL PROTECTED] wrote:
On Wed, 9 Jan 2008, Duft Markus wrote:
Bob Friesenhahn wrote:
On Tue, 8 Jan 2008, Ralf Wildenhues wrote:
General question before fixing this: on w32, should even plugins
have their DLLs go to $bindir?
Yes, i'd agree to this... ;o) If you
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 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 =
Shouldn't plug-in -type shared libraries be built with the -module
-avoid-version libtool flags? I think with those flags, such
libtool-built DLLs get installed in the libdir of the Makefile in
question, not libdir/../bin like normal DLLs.
--tml
___
On Tue, 8 Jan 2008, Ralf Wildenhues wrote:
General question before fixing this: on w32, should even plugins have
their DLLs go to $bindir?
Plugin modules should be installed adjacent to the .la files in the
directory the user specifies since the plugin module should be loaded
directly
Hm, sorry, as i reread my mail, i realized that the text is in the wrong
position ;) of course my comment is targeted ar bob's text, not ralf's
question...
Duft Markus wrote:
Bob Friesenhahn wrote:
On Tue, 8 Jan 2008, Ralf Wildenhues wrote:
General question before fixing this: on w32,
13 matches
Mail list logo
