fndLog4cplusBridge.hpp File Reference

Route ifw-fnd (FND*) log output into a log4cplus channel. More...

#include <string>

Go to the source code of this file.

Namespaces
namespace	ifw
namespace	ifw::core
namespace	ifw::core::utils
namespace	ifw::core::utils::base

Functions
void	ifw::core::utils::base::InstallFndLog4cplusBridge (const std::string &logger_name)
	Install the FND->log4cplus bridge as the process-wide ifw-fnd logger. Bridged FND* output goes to the log4cplus logger named logger_name (configure it in log.properties). Idempotent: does nothing if an ifw-fnd logger is already installed. Call once at startup, before anything logs via FND*.

Detailed Description

Route ifw-fnd (FND*) log output into a log4cplus channel.

Copyright

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

ifw-fnd defines a backend-agnostic logging abstraction (it must build on VLTSW too, so it cannot depend on log4cplus). Applications that run in the ELT/CII environment use log4cplus. This bridge lets such an application route the FND* output of any ifw-fnd-based library (e.g. camcom) into log4cplus, so all logs share one configuration (log.properties: levels, appenders, syslog).

It lives in ifw-core (which already depends on both log4cplus and ifw-fnd) rather than in ifw-fnd, keeping ifw-fnd backend-free. Every ELT app that mixes log4cplus with FND*-based libraries installs this single bridge.