Frederik Fouvry <[EMAIL PROTECTED]> writes:
> - I use *_LDADD. In that case, as far as I know, I cannot check
> for the libraries in the configuration anymore. Is it sensible
> to add AC_SUBST(program_LDADD) in configure.ac?
Let autoconf define and substitute a variable for each library to
Hi,
I have two applications (in different directories) in the
configure tree. They need to be linked with a different set of
libraries. What is the best way to proceed:
- using autoconf, I link the binaries with all libraries, even
though that is overkill.
- I use *_LDADD. In that case, as
Hello all,
I am developing a project (http://fireflier.sf.net), which uses
automake. I don't know a lot about automake, and so far i didnt find
documentation, which helps me with my problem - so any pointers in the
correct direction will be appreciated.
fireflier is a interactive firewall system w
Hi Bob!
Bob Friesenhahn wrote:
> On Tue, 31 Aug 2004, Gary V.Vaughan wrote:
> That sounds great, but in my case the input files are graphic image
> files so they would be rather unwieldy in here documents. Typically a
> file is read, processed using an algorithm, and then either its checksum
> is
On Tue, 31 Aug 2004, Gary V.Vaughan wrote:
Many scripts could be one-liners if Automake can produce a per-directory
test environment.
I made a stab at converting libtool to non-recursive make last year (I think)
and had much the same problem. I think the general solution is to move to an
Autote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Bob,
On 31 Aug 2004, at 06:08, Bob Friesenhahn wrote:
On Mon, 30 Aug 2004, Bob Friesenhahn wrote:
The $(srcdir) value passed is often essentially useless since it may
just be '.'. It is difficult for the Makefile to produce better
values except fo
