Re: custom install rules

2007-02-08 Thread Ralf Wildenhues
* Ralf Wildenhues wrote on Thu, Feb 08, 2007 at 12:53:29PM CET: > Almost. It should be > fooplug_LIBTOOLFLAGS = --tag=disable-static Erm. fooplug_la_LIBTOOLFLAGS.

Re: custom install rules

2007-02-08 Thread Ralf Wildenhues
* Christian Parpart wrote on Thu, Feb 08, 2007 at 10:45:13AM CET: > hm... okay, so assuming I've too DSOs in a directory, one shared library > (libfoo.so) and a plugin (fooplug.so), how would the rules then look like? > lib_LTLIBRARIES = libfoo.la > libfoo_la_SOURCES = libfoo.cpp > fooplugsdir =

Re: custom install rules

2007-02-08 Thread Christian Parpart
On Thursday 08 February 2007 09:29:13 Ralf Wildenhues wrote: > Hello Christian, > > * Christian Parpart wrote on Thu, Feb 08, 2007 at 07:18:18AM CET: > > I'd like to install some plugins, that usually do not need any .la or .a > > files to be installed (and even compiled). > > Use the `install-exec

Re: custom install rules

2007-02-08 Thread Ralf Wildenhues
Hello Christian, * Christian Parpart wrote on Thu, Feb 08, 2007 at 07:18:18AM CET: > > I'd like to install some plugins, that usually do not need any .la or .a > files > to be installed (and even compiled). Use the `install-exec-local' target to extend Automake's install rules, don't override

custom install rules

2007-02-07 Thread Christian Parpart
Hi, I'd like to install some plugins, that usually do not need any .la or .a files to be installed (and even compiled). However, libtool doesn't seem to allow some specific files not to be compiled that overloaded, so I'd like to post-remove the installed .{la,a} files. But what rule is usuall