Re: Automatically remove .libs directory

[Robert Boehne]

Hmmm, OK, I'm convinced.  After looking over the patch and reading
everyone's comments it is now apparent to me that libtool already
is removing files, so why not remove the directories too.
So I'm OK with the patch.  Thanks for my rapid education!

Cheers!

Robert 

Ossama Othman wrote:
> 
> Hi,
> 
> On Fri, Mar 09, 2001 at 06:23:13PM +0100, Peter Eisentraut wrote:
> > Robert Boehne writes:
> >
> > > I don't think that removing files during "make clean" is part of
> > > libtool's job, that is what Makefiles are for.
> >
> > If it's libtool's job to create them, and libtool wants to be a
> > transparent solution, then it is also libtools job to remove them.  Surely
> > you can do it in the makefile, but in reality you can do everything that
> > libtool does in a makefile, but it's nice that libtool encapsulates the
> > details so I don't have to worry about them.
> 
> I agree with Peter, especially since I was the one that suggested
> adding a "clean" option to Libtool. :-)
> 
> > > I realize you wouldn't necessarily have the name of this directory
> > > as libtool might generate different names on different platforms,
> > > but perhaps libtool could be patched to return this info instead?
> 
> The way I see it, Libtool should be able to "undo" what it has done.
> This implies being able to erase files/directories that it has
> created.  Suppose you're using libtool to generate a C++ shared
> library (assume ML branch for now) with template instantiations in it,
> then it is likely that the C++ compiler will generate a template
> repository.  However, template repository names are
> compiler-specific.  Some use files, while others use a directory with
> files inside that directory.  How is automake to know which template
> repository to erase?  Libtool already knows which compiler generated
> the template repository so it can easily determine how to erase it.
> You could certainly return this information from libtool, but then why
> isn't the same thing done when building a shared library?  I guess it
> all depends on how tighly coupled automake and libtool should be.
> 
> BTW, the template repository cleaning feature currently doesn't
> exist.  It's something that I've been thinking about implementing. :-)
> 
> -Ossama
> --
> Ossama Othman <address@hidden>
> Distributed Object Computing Laboratory, Univ. of California at Irvine
> 1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068  70E6 5EB7 5E71 F7A3 94A8
> 
> _______________________________________________
> Libtool-patches mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/libtool-patches

-- 
Robert Boehne             Software Engineer
Ricardo Software   Chicago Technical Center
TEL: (630)789-0003 x. 238
FAX: (630)789-0127
email:  address@hidden