| 1 |
Source: diagnostics |
| 2 |
Priority: extra |
| 3 |
Maintainer: Michael Tautschnig <[email protected]> |
| 4 |
Build-Depends: dpkg-dev (>= 1.22.5), dpkg-dev (>= 1.16.0~), debhelper (>= 9), automake, pkg-config, libtool, libltdl-dev (>= 2.4.2-1~), libace-dev (>= 5.7.7-3) [!hurd-i386], dh-autoreconf |
| 5 |
Standards-Version: 3.9.8 |
| 6 |
Section: libs |
| 7 |
Homepage: http://forsyte.at/software/diagnostics |
| 8 |
|
| 9 |
Package: libdiagnostics-dev |
| 10 |
Section: libdevel |
| 11 |
Architecture: any |
| 12 |
Depends: libdiagnostics0t64 (= ${binary:Version}), ${misc:Depends} |
| 13 |
Recommends: libace-dev |
| 14 |
Description: Logging, unittesting, and runtime diagnostics for C++ - development files |
| 15 |
Diagnostics is a unified framework for code annotation, logging, |
| 16 |
program monitoring, and unit-testing. |
| 17 |
. |
| 18 |
The annotations of diagnostics provide simple trace messages, tracing |
| 19 |
method entry and exit, checks (which potentially fail), asserts (which |
| 20 |
should never fail), invariance checking on method entry and exit, and |
| 21 |
a number of annotations for testing. |
| 22 |
. |
| 23 |
The annotations raise events which are can be observed and monitored. |
| 24 |
Using different loggers, the stream of logging events is used for |
| 25 |
logging or testing. |
| 26 |
. |
| 27 |
The package contains the needed headers and libraries for |
| 28 |
developing software using Diagnostics. |
| 29 |
|
| 30 |
Package: libdiagnostics0t64 |
| 31 |
Provides: ${t64:Provides} |
| 32 |
Replaces: libdiagnostics0 |
| 33 |
Breaks: libdiagnostics0 (<< ${source:Version}) |
| 34 |
Architecture: any |
| 35 |
Depends: ${shlibs:Depends}, ${misc:Depends} |
| 36 |
Description: Logging, unittesting, and runtime diagnostics for C++ - library |
| 37 |
Diagnostics is a unified framework for code annotation, logging, |
| 38 |
program monitoring, and unit-testing. |
| 39 |
. |
| 40 |
The annotations of diagnostics provide simple trace messages, tracing |
| 41 |
method entry and exit, checks (which potentially fail), asserts (which |
| 42 |
should never fail), invariance checking on method entry and exit, and |
| 43 |
a number of annotations for testing. |
| 44 |
. |
| 45 |
The annotations raise events which are can be observed and monitored. |
| 46 |
Using different loggers, the stream of logging events is used for |
| 47 |
logging or testing. |
| 48 |
. |
| 49 |
The package contains the libraries for running software linked against |
| 50 |
Diagnostics. |