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
From: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To: "Charles Wilson" <cwilson AT ece DOT gatech DOT edu>, <cygwin AT cygwin DOT com>
Subject: RE: [avail for test] libtool-devel-20030121-1
Date: Mon, 3 Feb 2003 21:02:55 +0100
Message-ID: <004d01c2cbbf$3da7bbb0$0a1c440a@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <3E3D8B4C.1040703@ece.gatech.edu>

Hi Chuck,
>    3) What I did:  create a binary wrapper -- an actual executable --
> named 'foo.exe' in the main build directory.  It is NOT the real
> foo.exe.  It simply exec's the shell script, which in turn sets up the
> environment and exec's the real .lib/foo.exe.  Eventually, the 'set up
> the environment' part could be moved into the binary wrapper itself, at
> least on cygwin/mingw -- but there are problems with that; libtool
> itself *sources* and parses the shell wrapper -- it can't do that with a
> binary wrapper.  So that's for later.  This works now, even if it is a
> bit kludgey.
>
> Unfortunately, it might lead to a FAQ: the shell wrapper contains a
> banner at the top that says "This is not the real foo.exe.  It is a
> wrapper" blah blah blah.  Plus, it's named 'foo' instead of 'foo.exe' --
> a tipoff for us windows denizens.  Now, you have:
>
> <builddir>/foo           : shell wrapper
> <builddir>/foo.exe       : binary wrapper
> <builddir>/.lib/foo.exe  : the real executable
>
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.

Ralf


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