Ralf Wildenhues wrote: > But this would still prevent automake to warn the user when he used > noinst_LTLIBRARIES = libfoo.la > lib_LTLIBRARIES = libfoo.la > > but really meant to use > if COND_FOO > noinst_LTLIBRARIES = libfoo.la > else > lib_LTLIBRARIES = libfoo.la > endif
automake could still _warn_ about it. What I'm complaining about is that it gives an error (exit code 1), although the purpose of the error - avoiding conflicts in -rpath options - is not met. > I'm sorry but I still fail to see the added value. automake goes a long way allowing to specify _what_ to compile, _what_ to install, and _what_ to distribute, instead of the _how_ to do it (in the ancient Makefile world). The "+=" augmentation of variables allows the programmer to make all these specifications independently. Here actually I'd like to have one tool specify what to compile (namely, libfoo.la), and other tool specify what to install (namely, libfoo.la as well). You force me to put both specifications into the same line in Makefile.am. This makes it impossible to have gnulib-tool generate one of them and have the other one written by hand. > gnulib-tool could be made smart enough to output the right thing in > the first place Do you have an idea how to do so without an additional command-line option? > or let configure compute where to put the library. How? I don't follow you here. Bruno
