GitLab

See bug #2367 for the fix-scaffolding.py tool.

Add a reset logging function to specific tests to ensure that the
logging is routed to the stream selected by the B10 environment
variables prior to each test that generates messages.

Add support of B10_LOGGER_DESTINATION to choose logging destination
for unit tests, and add tests to check that they work.  Also update
some documentation.

Allow default logging severity for unit tests to be specified
and overridden by an environment variable.

Added basic logger manager and its implementation, plus an untested
console appender.  Also modified logger_support_test to use that
appender and have got part way through creating a file logger test.

... the logical place for it.

Further changes after review.  Also removed some includes of
<iostream> left over from debugging.

Updated the initialization function to take the logger name.  Also
added code to detect (and log) if duplicate message IDs were
compiled into the system.

two spaces, one letter 'e' added

The introduction of logging caused problems when building BIND10
on a number of systems because up to date log4cxx support was not
available. (It appears that v0.9.8 is the minimum required, and a
number of distributions only have v0.9.7.)  For this reason, the
logging is being altered (for the moment) to withdraw log4cxx and
to write directly to the console.

The best solution seemed to be to split the basic API and the
implementation and to provide implementations for different logging
systems. (This was entered as ticket 529, but is being done now.)
The current commit leaves the logging system still using log4cxx,
but with the implementation split from the API.

A checkpoint of various modifications to the logging code in trac438.

git-svn-id: svn://bind10.isc.org/svn/bind10/branches/trac438@4169 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/branches/trac289@2733 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/branches/trac289@2730 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/branches/trac241@2490 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@1360 e5f2f494-b856-4b98-b285-d166d9295462

moved tests into unittests/ subdirectory
added boostlibs ldd flag if needed


git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@1321 e5f2f494-b856-4b98-b285-d166d9295462

This is based on ideas done in experiments/jreed-layout, but
I manually did this again.

Moved around directory structures.
A single python subdirectory under src/lib for single "isc" module.
No "cpp" directories.

No pyshared or includes symlink trees.

I tested running the c++ tests and python tests.
I tested running run_bind10.sh from source tree (with nothing installed).
I tested running bind10 from installed (after moving source).


git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@1120 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@1018 e5f2f494-b856-4b98-b285-d166d9295462

ticket #50 for full details)


git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@988 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/branches/jinmei-dnsrdata2@742 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/branches/parkinglot@530 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@320 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/branches/f2f200910@120 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@97 e5f2f494-b856-4b98-b285-d166d9295462

git-svn-id: svn://bind10.isc.org/svn/bind10/trunk@94 e5f2f494-b856-4b98-b285-d166d9295462