apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe Jr." <wr...@rowe-clan.net>
Subject Re: apu-util DBD back-ends
Date Wed, 15 Aug 2012 22:25:14 GMT
On 8/15/2012 4:03 PM, olli hauer wrote:
> Is there a way to find out if apu-util has support for different DBD
> backends like pgsql / sqlite3 / mysql ...
> 
> I could test if apr_dbd_$dbtype exist, but this looks like a dirty hack for me.
> I'm thinking more about an extension for apr-1-config for example
> 
> --- ./apu-config.in.orig
> +++ ./apu-config.in
> @@ -32,6 +32,9 @@
>  LDFLAGS="@APRUTIL_LDFLAGS@"
>  LDAP_LIBS="@LDADD_ldap@"
>  DBM_LIBS="@LDADD_dbm_db@ @LDADD_dbm_gdbm@ @LDADD_dbm_ndbm@"
> +DBD_LIBS="@LDADD_dbd_pgsql@ @LDADD_dbd_mysql@ @LDADD_dbd_sqlite2@ \
> +       @LDADD_dbd_sqlite3@ @LDADD_dbd_odbc@ @LDADD_dbd_freetds@ \
> +       @LDADD_dbd_oracle@"
> 
>  APRUTIL_LIBNAME="@APRUTIL_LIBNAME@"
> 
> @@ -130,6 +133,9 @@
>      --dbm-libs)
>      flags="$flags $DBM_LIBS"
>      ;;
> +    --dbd-libs)
> +    flags="$flags $DBD_LIBS"
> +    ;;
>      --includedir)
>      if test "$location" = "installed"; then
>          flags="$includedir"

That would make no sense for dynamic extensions.

Envision a packager who builds base (dynamic dbd) with minimal or no provider,
and then ships extention packages based on sql provider dependencies.





Mime
View raw message