httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sascha Schumann <sas...@schumann.cx>
Subject RE: APR builds concept broken horribly
Date Mon, 05 Jun 2000 19:07:34 GMT
On Mon, 5 Jun 2000 rbb@covalent.net wrote:

> 
> > > If the second, the same is done on Unix, so
> > > the executable doesn't get too large, but we end up having to dynamically
> > > link to things it doesn't need, which slows things down a bit.
> > 
> >     Are you still advocating enabling Pthreads in APR? That slows
> >     down things more than a bit, if Pthreads are not needed.
> 
> APR only includes pthreads if it is found/asked for.  This is two separate
> issues.  One is building APR, the other is building APR with
> Apache.  Either way, APR should be configured the same.  APR has
> everything possible turned on, unless it is specifically told to turn
> something off.  If you are building a prefork Apache, then you should be
> manually telling APR to build without threads.  But that is not this
> discussion.  :-)

    That is a fundamental disagreement, unfortunately.

>        dependancy:   file_io    time          
> package
> file_io                           x       
> threadroc               x
> locks                   x
> misc                    x  (for other child could be made its own library.)
> 
> Those are all of the dependancies I can think of off the top of my head.

    Ok, so we would need a tool which spits out a list of
    libraries which a program needs to be linked against, if it
    needs one or more APIs. I.e.

        $ apr-config file_io
        -Lpath/unix/file_io -lapr_file_io -Lpath/unix/time -lapr_time ...

    - Sascha



Mime
View raw message