From e8c56ad6bb5b571e7b5eabd07c3edf59ecdfd623 Mon Sep 17 00:00:00 2001 From: Arvid Norberg Date: Sun, 20 Mar 2005 10:34:07 +0000 Subject: [PATCH] *** empty log message *** --- Jamfile | 6 ++++-- docs/manual.html | 9 ++++----- docs/manual.rst | 7 +++---- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/Jamfile b/Jamfile index 20732e597..d3e130bea 100755 --- a/Jamfile +++ b/Jamfile @@ -34,14 +34,12 @@ project torrent static multi msvc:/Zc:wchar_t - debug:TORRENT_VERBOSE_LOGGING : usage-requirements ./include $(BOOST_ROOT) release:NDEBUG - debug:TORRENT_VERBOSE_LOGGING BOOST_ALL_NO_LIB ; @@ -94,6 +92,10 @@ LIBS = ; LIBS += wsock32 ; } +variant release_log : release : TORRENT_VERBOSE_LOGGING ; +variant debug_log : debug : TORRENT_VERBOSE_LOGGING ; + + lib torrent : src/$(SOURCES) diff --git a/docs/manual.html b/docs/manual.html index d2c15a5a6..4c030da15 100755 --- a/docs/manual.html +++ b/docs/manual.html @@ -245,7 +245,9 @@ windows format (c:/boost_1_32_0Jamfile will define -NDEBUG when it's building a release build.

+NDEBUG when it's building a release build. There are two other build variants available +in the Jamfile. debug_log and release_log, these two variants inherits from the +debug and release variants respectively, but adds extra logging (TORRENT_VERBOSE_LOGGIN).

@@ -265,10 +267,7 @@ other debug settings. +will log its traffic to a log file.
TORRENT_VERBOSE_LOGGING If you define this macro, every peer connection -will log its traffic to a log file. -This setting requires a debug build, i.e. -if you set NDEBUG aswell, no logs will be -written.
TORRENT_STORAGE_DEBUG This will enable extra expensive invariant diff --git a/docs/manual.rst b/docs/manual.rst index bbbdd0b57..213298725 100755 --- a/docs/manual.rst +++ b/docs/manual.rst @@ -151,7 +151,9 @@ The ``Jamfile`` can build both a release and debug version of libtorrent. In deb libtorrent will have pretty expensive invariant checks and asserts built into it. If you want to disable such checks (you want to do that in a release build) you can see the table below for which defines you can use to control the build. The ``Jamfile`` will define -``NDEBUG`` when it's building a release build. +``NDEBUG`` when it's building a release build. There are two other build variants available +in the ``Jamfile``. debug_log and release_log, these two variants inherits from the +debug and release variants respectively, but adds extra logging (``TORRENT_VERBOSE_LOGGIN``). +--------------------------------+-------------------------------------------------+ | macro | description | @@ -163,9 +165,6 @@ table below for which defines you can use to control the build. The ``Jamfile`` +--------------------------------+-------------------------------------------------+ | ``TORRENT_VERBOSE_LOGGING`` | If you define this macro, every peer connection | | | will log its traffic to a log file. | -| | This setting requires a debug build, i.e. | -| | if you set ``NDEBUG`` aswell, no logs will be | -| | written. | +--------------------------------+-------------------------------------------------+ | ``TORRENT_STORAGE_DEBUG`` | This will enable extra expensive invariant | | | checks in the storage, including logging of |