Alexandre Duret-Lutz wrote:
I see no problems with either or both...but I'd rather keep lt-foo.c around until 'make clean' (or libtool --mode=clean) time.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 youGood point. "libtool --mode=clean" won't currently get both of them. But automake's 'make clean' will (see below).
should ensure that `libtool --mode=clean rm -f foo.exe' erases `foo'.
(Or does Cygwin's `rm' erase both at once?)
No, it doesn't.
Yeah, I think this has come up before...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.
However, current automake "make clean" will at least attempt to delete all four of the following, whether they exist or not:
foo
foo.exe
.libs/foo (*)
.libs/foo.exe (*)
(*) by virtue of rm -rf'ing .libs
So, there's really no worry about cleaning up the shell wrapper or the "real" executable -- or the binary wrapper -- with present automake. But cleaning up the lt-foo.c file is an issue. I'd prefer to move it into .libs, but NOT erase it; automake's make clean will "get it" if it's in .libs (see rm -rf, above)
'Course, transitioning to libtool --mode=clean will mess that up, unless the problems you mention are addressed...
--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/