Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
Subject: Re: [avail for test] libtool-devel-20030121-1
Date: Mon, 03 Feb 2003 22:04:33 -0500
Lines: 51
Message-ID: <3E3F2DC1.8000105@ece.gatech.edu>
References: <3E3D8B4C DOT 1040703 AT ece DOT gatech DOT edu> <004d01c2cbbf$3da7bbb0$0a1c440a AT BRAMSCHE>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT main DOT gmane DOT org
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en



Ralf Habacker wrote:

> i've played a little with this stuff and have seen, that at least for cygwin
> there is an easier way to deal with this. Create a simple link from 'foo' to
> 'foo.exe' and Makes need are fullfilled.
> 
> See ltmain.sh:
> <snip>
>     # The program doesn't exist.
>     \$echo \"\$0: error: \$progdir/\$program does not exist\" 1>&2
>     \$echo \"This script is just a wrapper for \$program.\" 1>&2
>     echo \"See the $PACKAGE documentation for more information.\" 1>&2
>     exit 1
>   fi
> fi\
> "
> 	chmod +x $output
> +	ln -s $output $output$exeext
> 	fi
> 
> The single added line fix this.

It sure would have been nice if you'd mentioned this idea at some point 
over the past two months that I've been working on this, and CC:ing the 
cygwin list on the progress or lack of it.  (I also tried this at one 
point, and ran into problems; I don't recall what they were.  This was 
so easy to do that it didn't take long to implement or test -- and it 
failed, so I dropped it and it left very little impression on me about 
WHY it failed. Sorry.)

But, in any case, *even if it worked in all cases*, it's too late.  At 
this point, this IS the mechanism that libtool will use; it's been 
through the wringer with the folks on the automake list, libtool list, 
and has been tested on cygwin and mingw.  The symlink idea has not 
(plus, there's my earlier experience in which the symlink idea failed 
somehow).

the question now is, does the current implementation work, or not.  I'm 
not interested at this point in finding another mechanism.  I'm 
interested in working any kinks out of THIS one -- if there are any 
left.  I have beaten on it pretty hard, ya know.

But, I'm not being completely arbitrary here; there's more in store for 
the executable wrapper idea.  Eventually, I'd like to subsume all of the 
script wrapper's functionality into the executable wrapper, and do away 
with the script entirely.

--Chuck



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/