fndLog4cplusBridge.hpp File Reference

Routes ifw-fnd FND* logging into FCF's log4cplus. More...

Go to the source code of this file.

Namespaces
namespace	ifw
namespace	ifw::fcf
	ActionsEnable class source file.
namespace	ifw::fcf::devmgr
	actuatorLcsIf class header file.
namespace	ifw::fcf::devmgr::common
	ActionMgr class source file.

Functions
void	ifw::fcf::devmgr::common::InstallFndLog4cplusBridge ()
	Install an ifw::fnd::Logger that forwards FND* macros into log4cplus under the "uatools" logger. Idempotent: does nothing if an ifw-fnd logger is already installed.

Detailed Description

Routes ifw-fnd FND* logging into FCF's log4cplus.

Copyright

SPDX-FileCopyrightText: 2026 European Southern Observatory (ESO) SPDX-License-Identifier: LGPL-3.0-only

FCF processes use log4cplus for their own logs; ualib (and other ifw-fnd consumers) use the ifw-fnd Logger abstraction. Without a bridge they end up in two separate sinks with two different formats. This helper installs an ifw::fnd::Logger that forwards each FND* call into a log4cplus logger named "uatools", so everything lands in the same log file with one consistent format.

This is an FCF-local stop-gap (same role as the equivalent helper in ifw-ccf/common/). The canonical CII <-> ifw-fnd bridge is expected to land in ifw-core later; once it does, this header and its .cpp will be removed and the InstallFndLog4cplusBridge() calls in main() replaced with whatever ifw-core exposes.