Solving the "relink exe's" libtool problem [take 2]

Mon Jan 13 03:30:00 GMT 2003

>>> "Chuck" == Charles Wilson <cwilson@ece.gatech.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