Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of jorton@redhat.com designates
 66.187.237.31 as permitted sender)
Date: Tue, 24 Mar 2009 15:04:16 +0000
From: Joe Orton <jorton@redhat.com>
To: dev@apr.apache.org
Subject: Re: Modular APR
Message-ID: <20090324150415.GA20328@redhat.com>
Mail-Followup-To: dev@apr.apache.org
References: <20090324143922.GA20061@redhat.com> <49C8F4FA.8080309@sharp.fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <49C8F4FA.8080309@sharp.fm>
User-Agent: Mutt/1.5.18 (2008-05-17)
Organization: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor,
 Berkshire, SL4 1TE, United Kingdom.
  Registered in UK and Wales under Company Registration No. 03798903
  Directors: Michael Cunningham (USA), Brendan Lane (Ireland),
 Matt Parson (USA), Charlie Peters (USA)

On Tue, Mar 24, 2009 at 04:58:02PM +0200, Graham Leggett wrote:
> If I am understanding you correctly, for a library like dbd that  
> contains sub-libraries, you would have libapr-db, which in turn loads  
> dynamic modules called (say) libapr-db-pgsql (etc)?

apr_dbd.c would be linked into a library called libapr-db.  Any consumer 
of the DBD API will be adjusted to link in this library as well as 
libapr, e.g. by using something like "apu-2-config --modules=db".

If you build the DBD backends as DSOs, they are built as DSOs and are 
loaded at runtime exactly as currently.  If you link them in, they get 
linked into libapr-db and otherwise everything works exactly as 
currently.

Regards, Joe