compile-time options that preclude each other?

[Jan Parcel]

If I enable sql  at compile-time then my tests fail unless I also enable 
it at run-time.

Can I enable almost everything at config-time then have a generic .conf 
file that will be used for any application that does not have a specific 
conf file?

CONFIGURE_OPTIONS += --enable-auth-sasldb=yes
CONFIGURE_OPTIONS += --with-dblib=berkeley
CONFIGURE_OPTIONS += --with-dbpath=$(SASL_VARDIR)/sasl2db
CONFIGURE_OPTIONS += --with-saslauthd=/usr/sbin/saslauthd
CONFIGURE_OPTIONS += --with-gss_impl=seam
CONFIGURE_OPTIONS.32 += --with-plugindir=$(USRLIBDIR)/sasl2
CONFIGURE_OPTIONS.64 += --with-plugindir=$(USRLIBDIR)/sasl2/$(MACH64)
CONFIGURE_OPTIONS.32 += --with-sasldir=$(USRLIBDIR)/sasl2
CONFIGURE_OPTIONS.64 += --with-sasldir=$(USRLIBDIR)/sasl2/$(MACH64)
CONFIGURE_OPTIONS += --libdir=$(CONFIGURE_LIBDIR.$(BITS))
CONFIGURE_OPTIONS += --with-ipctype=doors
CONFIGURE_OPTIONS += --with-ldap=/usr
CONFIGURE_OPTIONS += --enable-sample=yes
CONFIGURE_OPTIONS += --enable-sql=yes
CONFIGURE_OPTIONS += --enable-ldaplb=yes
CONFIGURE_OPTIONS += --with-mysql=$(SASL_VARDIR)
# postfix or AD might need --enable-login and --enable-ntlm
CONFIGURE_OPTIONS += --enable-login=yes
CONFIGURE_OPTIONS += --enable-ntlm=yes

What does "rooted in dir" mean?