Message-ID: <4A6ED94B.8020003@gmail.com>
Date: Tue, 28 Jul 2009 11:56:11 +0100
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: How to install-libLTLIBRARIES dll to bin?
References: <6910a60907272310q54f29289l454117aff82afd5a@mail.gmail.com>
In-Reply-To: <6910a60907272310q54f29289l454117aff82afd5a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Reini Urban wrote:
> I have an issue with properly autotooled + libtoolized shared libraries
> where the resulting dll should end up in bindir instead of libdir.

  Yeh, me too.  I have a horrible hack in the distro gcc that ascends
directories until it finds ...../lib/ and replaces that with ..../bin/

> Can we cygwin-spezialize that either in automake or libtool?
> The --mode=install $(DESTDIR)$(libdir) looks like a job for automake
> but only libtool knows about the .dll
> in contrast to the .dll.a .la and .a
> Maybe libtool --mode=install can outsmart $libdir in the dll case.
> Or better automake can check for the dll and install this into bindir.

  Only libtool knows about the DLL.  Only the Makefile knows about the setting
of $bindir from configure.  Currently however the Makefile only passes the
path to the output in $libdir.  Therefore ISTM that the only correct solution
is to add a --bindir= option to libtool and modify automake or libtoolise to
ensure it gets passed by the makefiles when they invoke libtool.

    cheers,
      DaveK

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple