Re: self contained library

[Ronald Landheer-Cieslak]

The method will still work - just don't link to the C library statically, 
but do so for everything else (assuming you have static versions 
available, and taking into account that some code may need special 
compilation options to know it's going to be in a shared library, so don't 
use the .a file produced by Libtool without prejudice.

rlc


On Fri, 14 Mar 2003, Ricardo Fabbri wrote:

> On Fri, 14 Mar 2003, Ronald Landheer-Cieslak wrote:
> 
> > Do you mean by "self-contained" that it should even contain the C library
> > functions it uses?
> >
> 
> No.
> 
> I don't want the C library and system libraries to be in the "self-contained"
> library.  I will require the user to have libc6, for example.  What I do not
> want is non-programmers having to install or compile a whole list of not very
> common dependencies (which is numerous for my project).
> 
> With Linux being so widespread, there are many applications of which users are
> very naive and are not willing to install the dependencies. I wish I could be
> programming just for sensible Unix users, but that's not always the case for 
> my
> library.
> 
> Ricardo.
> 
> --
>   Ricardo Fabbri, Cybernetic Vision Research Group, USP, Brazil.
>   http://cyvision.if.sc.usp.br/~rfabbri
> 
> 
> 
> _______________________________________________
> Libtool mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/libtool
>