Commit ed1431b5 authored by Tomek Mrugalski's avatar Tomek Mrugalski 🛰
Browse files

[github40] --with-dhcp-XXX renamed to --with-XXX

Merge branch 'with-dhcp' of https://github.com/andreipavelQ/kea into github40

# Conflicts:
#	doc/guide/install.xml
parents 4314a562 a2d03ca4
......@@ -609,8 +609,8 @@ AX_CRYPTO
# the --with-mysql-config (default to /usr/bin/mysql-config). By default,
# the software is not built with MySQL support enabled.
mysql_config="no"
AC_ARG_WITH([dhcp-mysql],
AC_HELP_STRING([--with-dhcp-mysql=PATH],
AC_ARG_WITH([mysql],
AC_HELP_STRING([--with-mysql=PATH],
[path to the MySQL 'mysql_config' script (MySQL is used for the DHCP database)]),
[mysql_config="$withval"])
......@@ -622,7 +622,7 @@ fi
if test "$MYSQL_CONFIG" != "" ; then
if test -d "$MYSQL_CONFIG" -o ! -x "$MYSQL_CONFIG" ; then
AC_MSG_ERROR([--with-dhcp-mysql should point to a mysql_config program])
AC_MSG_ERROR([--with-mysql should point to a mysql_config program])
fi
MYSQL_CPPFLAGS=`$MYSQL_CONFIG --cflags`
......@@ -663,8 +663,8 @@ AC_CHECK_HEADERS(sys/filio.h,,,)
AM_CONDITIONAL(HAVE_MYSQL, test "$MYSQL_CONFIG" != "")
pg_config="no"
AC_ARG_WITH([dhcp-pgsql],
AC_HELP_STRING([--with-dhcp-pgsql=PATH],
AC_ARG_WITH([pgsql],
AC_HELP_STRING([--with-pgsql=PATH],
[path to the PostgreSQL 'pg_config' script]),
[pg_config="$withval"])
......@@ -676,7 +676,7 @@ fi
if test "$PG_CONFIG" != "" ; then
if test -d "$PG_CONFIG" -o ! -x "$PG_CONFIG" ; then
AC_MSG_ERROR([--with-dhcp-pgsql should point to a pg_config program])
AC_MSG_ERROR([--with-pgsql should point to a pg_config program])
fi
PGSQL_CPPFLAGS=`$PG_CONFIG --cppflags`
......
......@@ -101,7 +101,7 @@ hasn't been written yet.
See @ref unitTests for instructions on how to run unit-tests. If you
happen to touch any database related code, make sure you compile
your code with @c --with-dhcp-mysql, @c --with-dhcp-pgsql and/or
your code with @c --with-mysql, @c --with-pgsql and/or
@c --with-cql as needed. For example, if you change something
substantial, make sure the other compilation options still work.
......@@ -122,7 +122,7 @@ documentation, use \c --enable-generate-docs. If you are modifying DHCP
code, you are likely to be interested in enabling a non-default database
backends for DHCP. Note that if the backend is not enabled,
the database-specific unit-tests are skipped. To enable the MySQL backend,
use the switch \c --with-dhcp-mysql; for PostgreSQL, use \c --with-dhcp-pgsql.
use the switch \c --with-mysql; for PostgreSQL, use \c --with-pgsql.
A complete list of all switches can be obtained with the command:
@code
......
......@@ -130,7 +130,7 @@ The following environment variable can affect the unit tests:
%@endverbatim
The unit tests are run automatically when "make check" is executed (providing
that Kea has been build with the \c --with-dhcp-mysql switch (see the installation
that Kea has been build with the \c --with-mysql switch (see the installation
section in the <a href="http://kea.isc.org/docs/kea-guide.html">Kea Administrator
Reference Manual</a>).
......@@ -256,7 +256,7 @@ local all postgres trust
that runs tests. Use caution!
The unit tests are run automatically when "make check" is executed (providing
that Kea has been build with the \c --with-dhcp-pgsql switch (see the installation
that Kea has been build with the \c --with-pgsql switch (see the installation
section in the <a href="http://kea.isc.org/docs/kea-guide.html">Kea Administrator
Reference Manual</a>).
......
......@@ -159,7 +159,7 @@ Debian and Ubuntu:
<listitem>
<para>
The MySQL client and the client development libraries, when using
the --with-dhcp-mysql configuration flag to build the Kea MySQL
the --with-mysql configuration flag to build the Kea MySQL
database backend. In this case an instance of the MySQL server
running locally or on a machine reachable over a network
is required. Note that
......@@ -170,7 +170,7 @@ Debian and Ubuntu:
<listitem>
<para>
The PostgreSQL client and the client development libraries, when
using the --with-dhcp-pgsql configuration flag to build the Kea
using the --with-pgsql configuration flag to build the Kea
PostgreSQL database backend. In this case an instance of the
PostgreSQL server running locally or on some other machine,
reachable over the network from the machine running Kea, is
......@@ -321,7 +321,7 @@ Debian and Ubuntu:
</varlistentry>
<varlistentry>
<term>--with-dhcp-mysql</term>
<term>--with-mysql</term>
<listitem>
<simpara>
Build Kea with code to allow it to store leases (and access
......@@ -331,7 +331,7 @@ Debian and Ubuntu:
</varlistentry>
<varlistentry>
<term>--with-dhcp-pgsql</term>
<term>--with-pgsql</term>
<listitem>
<simpara>
Build Kea with code to allow it to store leases (and access
......@@ -392,7 +392,7 @@ Debian and Ubuntu:
<screen>$ <userinput>./configure \
--with-boost-include=/usr/pkg/include \
--with-dhcp-pgsql=/usr/local/bin/pg_config \
--with-pgsql=/usr/local/bin/pg_config \
--prefix=/opt/kea</userinput></screen>
</para>
......@@ -524,12 +524,12 @@ Debian and Ubuntu:
<para>
Build and install Kea as described in <xref linkend="installation"/>, with
the following modification. To enable the MySQL database code, at the
"configure" step (see <xref linkend="configure"/>), the --with-dhcp-mysql switch
"configure" step (see <xref linkend="configure"/>), the --with-mysql switch
should be specified:
<screen><userinput>./configure [other-options] --with-dhcp-mysql</userinput></screen>
If MySQL was not installed in the default location, the location of the MySQL
<screen><userinput>./configure [other-options] --with-mysql</userinput></screen>
If MySQL was not installed in the default location, the location of the MySQL
configuration program "mysql_config" should be included with the switch, i.e.
<screen><userinput>./configure [other-options] --with-dhcp-mysql=<replaceable>path-to-mysql_config</replaceable></userinput></screen>
<screen><userinput>./configure [other-options] --with-mysql=<replaceable>path-to-mysql_config</replaceable></userinput></screen>
</para>
<para>
See <xref linkend="mysql-database-create"/> for details regarding
......@@ -546,12 +546,12 @@ Debian and Ubuntu:
<para>
Build and install Kea as described in <xref linkend="installation"/>, with
the following modification. To enable the PostgreSQL database code, at the
"configure" step (see <xref linkend="configure"/>), the --with-dhcp-pgsql switch
"configure" step (see <xref linkend="configure"/>), the --with-pgsql switch
should be specified:
<screen><userinput>./configure [other-options] --with-dhcp-pgsql</userinput></screen>
If PostgreSQL was not installed in the default location, the location of the PostgreSQL
<screen><userinput>./configure [other-options] --with-pgsql</userinput></screen>
If PostgreSQL was not installed in the default location, the location of the PostgreSQL
configuration program "pg_config" should be included with the switch, i.e.
<screen><userinput>./configure [other-options] --with-dhcp-pgsql=<replaceable>path-to-pg_config</replaceable></userinput></screen>
<screen><userinput>./configure [other-options] --with-pgsql=<replaceable>path-to-pg_config</replaceable></userinput></screen>
</para>
<para>
See <xref linkend="pgsql-database-create"/> for details regarding
......
......@@ -1745,7 +1745,7 @@ TEST_F(DORATest, changingCircuitId) {
// Starting tests which require MySQL backend availability. Those tests
// will not be executed if Kea has been compiled without the
// --with-dhcp-mysql.
// --with-mysql.
#ifdef HAVE_MYSQL
/// @brief Test fixture class for the test utilizing MySQL database backend.
......@@ -1778,7 +1778,7 @@ TEST_F(DORAMySQLTest, multiStageBoot) {
// Starting tests which require MySQL backend availability. Those tests
// will not be executed if Kea has been compiled without the
// --with-dhcp-pgsql.
// --with-pgsql.
#ifdef HAVE_PGSQL
/// @brief Test fixture class for the test utilizing PostgreSQL database backend.
......
......@@ -641,7 +641,7 @@ TEST_F(JSONFileBackendTest, defaultLeaseDbBackend) {
// Starting tests which require MySQL backend availability. Those tests
// will not be executed if Kea has been compiled without the
// --with-dhcp-mysql.
// --with-mysql.
#ifdef HAVE_MYSQL
/// @brief Test fixture class for the tests utilizing MySQL database
......
......@@ -628,7 +628,7 @@ TEST_F(JSONFileBackendTest, defaultLeaseDbBackend) {
// Starting tests which require MySQL backend availability. Those tests
// will not be executed if Kea has been compiled without the
// --with-dhcp-mysql.
// --with-mysql.
#ifdef HAVE_MYSQL
/// @brief Test fixture class for the tests utilizing MySQL database
......
......@@ -23,12 +23,12 @@
- The MySQL lease manager uses the freely available MySQL as its backend
database. This is not included in Kea DHCP by default:
the \--with-dhcp-mysql switch must be supplied to "configure" for support
the \--with-mysql switch must be supplied to "configure" for support
to be compiled into the software.
- The PostgreSQL lease manager uses the freely available PostgreSQL as its
backend database. This is not included in Kea DHCP by default:
the \--with-dhcp-pgsql switch must be supplied to "configure" for
the \--with-pgsql switch must be supplied to "configure" for
support to be compiled into the software.
@section dhcpdb-instantiation Instantiation of Lease Managers
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment