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
To:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
Cc:	automake-patches AT gnu DOT org, libtool-patches AT gnu DOT org, cygwin AT cygwin DOT com,
	mingw-users AT lists DOT sourceforge DOT net
Subject:	Re: Solving the "relink exe's" libtool problem [take 2]
From:	Alexandre Duret-Lutz <duret_g AT lrde DOT epita DOT fr>
X-Home-Page:	http://gadl.free.fr/
X-GPG-Keyserver:	http://pgp.mit.edu/
X-GPG-Fingerprint:	FCA0 8615 0211 941A 2AB9 FA66 3859 C03B 2E23 6E47
Date:	Mon, 13 Jan 2003 00:19:28 +0100
In-Reply-To:	<3E20BF9A.4080400@ece.gatech.edu> (Charles Wilson's message of
	"Sat, 11 Jan 2003 20:06:34 -0500")
User-Agent:	Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu)
References:	<3E19C657 DOT 1040904 AT ece DOT gatech DOT edu>
	<2003-01-09-17-11-09+16471+duret_g AT lrde DOT epita DOT fr>
	<3E1DE146 DOT 8030901 AT ece DOT gatech DOT edu>
	<2003-01-09-23-01-51+2104+duret_g AT lrde DOT epita DOT fr>
	<3E20BF9A DOT 4080400 AT ece DOT gatech DOT edu>
MIME-Version:	1.0
Message-ID:	<2003-01-13-00-19-29+30521+duret_g@lrde.epita.fr>
X-Attribution:	adl

>>> "Chuck" == Charles Wilson <cwilson AT ece DOT gatech DOT edu> writes:

[...]

 Chuck> I left the shell wrapper where it was, in the build directory.  When
 Chuck> creating the shell wrapper, libtool will also create lt-${prog}.c and
 Chuck> compile it using
 Chuck> $run $LTCC -s -o ${prog}.exe lt-${prog}.c

 Chuck> So, you end up with:

 Chuck> <builddir>/foo           (shell wrapper)
 Chuck> <builddir>/foo.exe       (binary wrapper)
 Chuck> <builddir>/lt-foo.c
 Chuck> <builddir>/.libs/foo.exe (the real executable)

Any way lt-foo.c could go into .libs/?  Or just be erased after
foo.exe has been built?  Maybe both?

Also I if you don't move `foo' to `.libs/' I think you
should ensure that `libtool --mode=clean rm -f foo.exe' 
erases `foo'.  (Or does Cygwin's `rm' erase both at once?)

Right now Automake doesn't use `--mode=clean'.  Maybe Automake
1.8 could start doing this so we don't have to hardcode this
sort of knowledge.

[...]
-- 
Alexandre Duret-Lutz


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

- Raw text -