Le jeudi 20 décembre 2007 à 00:42 +0100, Manuel Prinz a écrit : > > Am Mittwoch, den 19.12.2007, 08:40 -0500 schrieb Adam C Powell IV: > > I think the confusion is: the .la files are not the static libs, > they > > are libtool metadata files. The -dev package needs to include > the .a > > static libs. The .la files are completely optional, and there's > some > > difference of opinion on whether or not they are beneficial. If > > upstream installs them, I'd put them in the -dev package. > > The reasoning for dropping the .la files was that we don't build .a > files. My understanding is that .la is useless without .a, so > installing > them did not make much sence to me. Or am I wrong here? You are wrong, sorry :p Just open one .la file and you will understand.
They are supposed to hide the complexity of dynamic libraries. For example, if you are linking thanks to libtool with a dyn library, you can use the .la file to link it. And if this library has dependencies, the .la will tell you that. It will also provide you the name of the library, linker flags, version Example: # grep dependency myGreatLibraryWhichNeedsPcre.la dependency_libs=' -L/usr/lib -lpcreposix -lpcre' I hope I am clear on this ;) Sylvestre
signature.asc
Description: Ceci est une partie de message numériquement signée