premiere
/
premiere-libtorrent
2
2
Fork 1
Code Issues Pull Requests Releases Wiki Activity

*** empty log message ***

This commit is contained in:
Arvid Norberg 2005-03-20 10:34:07 +00:00
parent 6ff7e76ab2
commit e8c56ad6bb
3 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Jamfile
View File

@ -34,14 +34,12 @@ project torrent
<link>static <link>static
<threading>multi <threading>multi
<toolset>msvc:<cxxflags>/Zc:wchar_t <toolset>msvc:<cxxflags>/Zc:wchar_t
<variant>debug:<define>TORRENT_VERBOSE_LOGGING
: usage-requirements : usage-requirements
<include>./include <include>./include
<include>$(BOOST_ROOT) <include>$(BOOST_ROOT)
<variant>release:<define>NDEBUG <variant>release:<define>NDEBUG
<variant>debug:<define>TORRENT_VERBOSE_LOGGING
<define>BOOST_ALL_NO_LIB <define>BOOST_ALL_NO_LIB
; ;
@ -94,6 +92,10 @@ LIBS = ;
LIBS += wsock32 ; LIBS += wsock32 ;
} }
variant release_log : release : <define>TORRENT_VERBOSE_LOGGING ;
variant debug_log : debug : <define>TORRENT_VERBOSE_LOGGING ;
lib torrent lib torrent
: :
src/$(SOURCES) src/$(SOURCES)

9
docs/manual.html
View File

@ -245,7 +245,9 @@ windows format (<tt class="docutils literal"><span class="pre">c:/boost_1_32_0</
libtorrent will have pretty expensive invariant checks and asserts built into it. If you 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 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 <tt class="docutils literal"><span class="pre">Jamfile</span></tt> will define table below for which defines you can use to control the build. The <tt class="docutils literal"><span class="pre">Jamfile</span></tt> will define
<tt class="docutils literal"><span class="pre">NDEBUG</span></tt> when it's building a release build.</p> <tt class="docutils literal"><span class="pre">NDEBUG</span></tt> when it's building a release build. There are two other build variants available
in the <tt class="docutils literal"><span class="pre">Jamfile</span></tt>. debug_log and release_log, these two variants inherits from the
debug and release variants respectively, but adds extra logging (<tt class="docutils literal"><span class="pre">TORRENT_VERBOSE_LOGGIN</span></tt>).</p>
<table border="1" class="docutils"> <table border="1" class="docutils">
<colgroup> <colgroup>
<col width="40%" /> <col width="40%" />
@ -265,10 +267,7 @@ other debug settings.</td>
</tr> </tr>
<tr><td><tt class="docutils literal"><span class="pre">TORRENT_VERBOSE_LOGGING</span></tt></td> <tr><td><tt class="docutils literal"><span class="pre">TORRENT_VERBOSE_LOGGING</span></tt></td>
<td>If you define this macro, every peer connection <td>If you define this macro, every peer connection
will log its traffic to a log file. will log its traffic to a log file.</td>
This setting requires a debug build, i.e.
if you set <tt class="docutils literal"><span class="pre">NDEBUG</span></tt> aswell, no logs will be
written.</td>
</tr> </tr>
<tr><td><tt class="docutils literal"><span class="pre">TORRENT_STORAGE_DEBUG</span></tt></td> <tr><td><tt class="docutils literal"><span class="pre">TORRENT_STORAGE_DEBUG</span></tt></td>
<td>This will enable extra expensive invariant <td>This will enable extra expensive invariant

7
docs/manual.rst
View File

@ -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 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 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 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 | | 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 | | ``TORRENT_VERBOSE_LOGGING`` | If you define this macro, every peer connection |
| | will log its traffic to a log file. | | | 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 | | ``TORRENT_STORAGE_DEBUG`` | This will enable extra expensive invariant |
| | checks in the storage, including logging of | | | checks in the storage, including logging of |