> From: Branko Cibej [mailto:brane@xbc.nu]
> Sent: Friday, October 31, 2003 12:01 AM
> Hm, I just had a thought. We're not really using apr-util's DB
> functions, so it's all right if they use sdbm instead of BDB. We're only
> using the APU_WANT mechanism to include db.h in _our_ code, and our
> generated project files _do_ know where to find that file.
The apr-util windows build system is extremely inflexible, which
is where this stems from. Basically you need to set all things by
hand instead of letting something similar as configure figure it
out.
> So how about this:
>
> --- apu.hw.~1.14.~ 2003-10-30 23:15:17.000000000 +0100
> +++ apu.hw 2003-10-30 23:58:50.000000000 +0100
> @@ -144,7 +144,10 @@
> */
> #define APU_HAVE_SDBM 1
> #define APU_HAVE_GDBM 0
> +
> +#ifndef APU_HAVE_DB
> #define APU_HAVE_DB 0
> +#endif
>
> Then we define APU_HAVE_DB to 1 in our project files, and things will
> Just Work.
I now remember what I did: I just flipped the APU_HAVE_DB define to 1
in the source. And since I didn't build with apache on windows, the
problem wasn't that obvious.
I'll drop this patch in apr-util risking it to be shot down...
Hopefully we'll be able to improve the apr-util build system at some
point.
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 31 12:23:47 2003