| 1 |
> |
| 2 |
> When you're going into the autotools hell. Also completely |
| 3 |
> obsoleted before it even came into existence. A set of well- |
| 4 |
> designed shell functions could do the job *much* better. |
| 5 |
> |
| 6 |
|
| 7 |
While porting to cygwin I can be happy when they use it. For my first |
| 8 |
impression those libraries are more easy to port. They produce |
| 9 |
libraries with a *.dll.a suffix like the native libraries of Cygwin. |
| 10 |
|
| 11 |
The other example is libz. AFAIK it has a manually written configure |
| 12 |
script. It generates libz.so. bzip2 ends up in error messages until I |
| 13 |
build it statically. |
| 14 |
|
| 15 |
I still try to understand the relation of shared libraries and dynamic |
| 16 |
libraries. I read that dynamic libraries are linked at runtime. I also |
| 17 |
read, that you can dynamically link againgst a shared as well as |
| 18 |
against a normal library. |
| 19 |
|
| 20 |
But isn't a normal library also shared when multiple programs link it |
| 21 |
at runtime or does shared library mean it is shared in memory (PIC)? |
| 22 |
|
| 23 |
Al |
Archives