2
0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-29 13:07:50 +00:00

[3109] Update text

This commit is contained in:
Mukund Sivaraman 2013-09-12 12:50:41 +05:30
parent 19cb906413
commit 37bb1f516e

View File

@ -76,7 +76,7 @@ gtest) as a base for our C++ unit-tests. See
http://code.google.com/p/googletest/ for details. For Python unit-tests,
we use the its \c unittest library which is included in Python. You must
have \c gtest installed or at least extracted in a directory before
compiling BIND10 unit-tests. To enable unit-tests in BIND10, use
compiling BIND10 unit-tests. To enable unit-tests in BIND10, use:
@code
./configure --with-gtest=/path/to/your/gtest/dir
@ -88,13 +88,13 @@ or
./configure --with-gtest-source=/path/to/your/gtest/dir
@endcode
There are other useful switches passed to configure. It is always a good
idea to use --enable-logger-checks, which does sanity checks on logger
There are other useful switches which can be passed to configure. It is always a good
idea to use \c --enable-logger-checks, which does sanity checks on logger
parameters. If you happen to modify anything in the documentation, use
--enable-generate-docs. If you are modifying DHCP code, you are likely
to be interested in MySQL backend for DHCP. Keep note that if the backend
is not enabled, MySQL specific unit-tests are skipped, too. From that
perspective, it is useful to use --with-dhcp-mysql parameter. For a
\c --enable-generate-docs. If you are modifying DHCP code, you are likely
to be interested in enabling the MySQL backend for DHCP. Note that if the backend
is not enabled, MySQL specific unit-tests are skipped. From that
perspective, it is useful to use \c --with-dhcp-mysql. For a
complete list of all switches, use:
@code