Message-ID: <4A7F30FC.7030506@gmail.com>
Date: Sun, 09 Aug 2009 21:26:36 +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> <4A6ED94B.8020003@gmail.com> <4A7E725C.8010706@users.sourceforge.net> <4A7ED3C9.70700@cwilson.fastmail.fm> <4A7F03EA.9030101@gmail.com> <4A7F2C02.80409@cwilson.fastmail.fm>
In-Reply-To: <4A7F2C02.80409@cwilson.fastmail.fm>
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

Charles Wilson wrote:

> OTOH, Dave, can you see any reason why Yaakov's simpler "hack" as
> modified by your 19:21:26UTC message shouldn't *ALSO* go in, along with
> --bindir support?  It (1) seems like a reasonable approach, (2) doesn't
> suffer from the "hey that dir doesn't exist yet" problem, and (3)
> doesn't appear to have much potential for causing harm in normal usage.

  Yes, I think it's a good patch.  The existing code is a heuristic, and this
improves the heuristic in a common failure case without breaking it in other
cases, I think it should go in.

> and append a ../bin to it -- which works if THE $libdir and THE $bindir
> are actually siblings.  Since, for gcc, they may not be, --bindir is
> actually a cleaner approach in that case.  But in general,...

  I don't think you needed to qualify that by saying "for gcc they may not be";
it applies to anything that uses autotools.  As long as configure offers the
user --bindir, --libdir, and all these other options for freely renaming and
re-laying-out the $prefix structure during a configure and build, I think that
we need to support them, with a more general approach that will DTRT no matter
how the user configures their build.

    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