X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.5 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4A7F2C02.80409@cwilson.fastmail.fm>
Date: Sun, 09 Aug 2009 16:05:22 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: How to install-libLTLIBRARIES dll to bin?
References: <6910a60907272310q54f29289l454117aff82afd5a AT mail DOT gmail DOT com> <4A6ED94B DOT 8020003 AT gmail DOT com> <4A7E725C DOT 8010706 AT users DOT sourceforge DOT net> <4A7ED3C9 DOT 70700 AT cwilson DOT fastmail DOT fm> <4A7F03EA DOT 9030101 AT gmail DOT com>
In-Reply-To: <4A7F03EA.9030101@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Dave Korn wrote:
>> This part is messy -- and unnecessary for the intended use case. In gcc,
>> all you need to do is explicitly modify the Makefile.am's to pass the
>> necessary option. You don't need to do anything to automake or
>> libtoolize, AFAICT.
> 
>   That's actually my /real/ plan for GCC, but I figured at some point it would
> be a nice extension to do it automatically.

Right, which is why I asked Yaakov about his specific use cases. If he
had 200 instances, then adding --bindir=\${bindir} to libfoo_la_LDFLAGS
as a private cygwin patch, or officially upstream in 200 project foo's
would be...problematic.  With just two or three, then a gradual
approach, adding --bindir to libtool first, and then later adding
support if necessary to automake, becomes feasible.

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.

It doesn't solve your gcc problem[*], but won't interfere with it,
either -- espeically if you modify gcc to explicitly use the new
--bindir support.

[*] actually, it might: /usr/lib/gcc/i686-pc-cygwin/4.3.2/ *is* in a
subdir of THE $libdir...so Yaakov's approach will turn
  /usr/lib/gcc/i686-pc-cygwin/4.3.2/
into
  /usr/lib
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,...

--
Chuck

--
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