View Single Post
Posts: 2,006 | Thanked: 3,351 times | Joined on Jun 2010 @ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
#28
Originally Posted by reinob View Post
That's why those bright heads split the packages between "normal" and "development". It may be the right thing to do for most people. I myself tend to be very very conservative with "modern" technology
I tend to be conservative, but I have seen Debian packaging before I have seen a Makefile, so instead of trying to use both Debian packaging and Makefile at the same time, I aim to use only Debian packaging, plain, without .configure files or whatever.
Originally Posted by reinob View Post
The .a is the static counterpart of the .so, so you need the .a if you want to statically link a library (as opposed to using the .so, for which you need the .la).

The funny thing is that most programs are developed using the traditional way, i.e. a Makefile that builds the program. make install usually installs everything (yes, including .a and .la, etc.)
'Everything' sounds ominously complicated.
Originally Posted by reinob View Post
The .deb packagers (maintainers I think they're called) take that and generally make a mess of it by adding dependencies, using more-or-less common sense (unfortunately not always) and decide to strip one thing or the other or (in the case of Maemo) to "optify" the package after-the-fact (instead of compiling with the appropriate --prefix).

It's actually pretty incredible that things like Maemo, Debian and Ubuntu actually work OK-ish
Agree. I use gcc flag "-shared", and see neither tail nor whiskers of 'additional' .a or .la files - only the needed .so file.
Best wishes.
 

The Following User Says Thank You to Wikiwide For This Useful Post: