Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of scarleton@gmail.com designates
 209.85.216.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        b=s9uedSThgzKqpMr2nckk2jRAs/mKFv2M6dk/0NuA6pcRq8v+wG9MBvPpH9H1G9ntLs
         searC5SuugLDihpyG6IJBsIuaENZFOeCrGg5jaqnoy51aXO1ucg/UppYY//YAhN/eUm+
         Pne5Zbd/7w/88yJuVy9DzP6jvu7B4ZWSQE2Vg=
MIME-Version: 1.0
Sender: scarleton@gmail.com
Date: Mon, 5 Jul 2010 13:00:29 -0400
Message-ID: <AANLkTikyhpgdaWHSy5_1DGY70fiYjVl446TqIDkFtmtC@mail.gmail.com>
Subject: Understanding apu_dso_load
From: Sam Carleton <scarleton@miltonstreet.com>
To: dev@apr.apache.org
Content-Type: text/plain; charset=UTF-8

Ok, I have succeeded in getting apr_dbd_sqlite3.c to compile with the
correct runtime, now it is time to use it.  Today I am going to be
using it on Windows, later on Unix, so I need to understand how to
load it in both worlds...

It looks like the mod_dbd calls apu_dso_load() to load the driver.  In
looking at the code, it appears that the non win32 platforms need to
have the compiler macro APU_DSO_LIBDIR set.  This leads to two
questions:

1: On the win32 machines, where does the system look for the drivers?
In the enviornment path?

2: In the non win32 world, I cannot hard code paths, is there some
other option to tell apu_dso_load() where to look for the drivers?

Sam