Re: dynamic versus statically linked libraries
>
> 6) If I have an LSB compliant application that dynamically links an LSB
> compliant library that is not part of the LSB specification, then it is no
> longer LSB compliant because of its dependency.
>
> 7) If I have an LSB compliant application that statically links an LSB
> compliant library that is not part of the LSB specification, then it
> remains LSB complaint.
>
> Given the axioms above, then a private (non *PLed) application cannot use
> *any* LSB compliant *PLed library that is not in the LSB specifiction,
> because #7 would force the private application to become *PLed.
>
> To correct this, then axiom #7 should be dropped and #6 should allow the
> LSB compliant application to remain LSB compliant.
>
> Am I wrong? :-) Please help clarify any misunderstandings...
>
Yes. #6 is the mistaken axiom: you are free to include the particular
dynamic library with your application. LSB doesn't care if you link
static or dynamic, you are just not allowed to *require the a priori
presence of the library on your system*. Thus, the additional library
becomes part of the application.
-hpa
Reply to: