2015-03-05 12:22 GMT+01:00 Jürgen E. <[email protected]>: > Hi Alessandro, > > On Wed, 04. Mar 2015 at 21:38:44 +0100, Alessandro Pasotti wrote: >> I cannot understand the reasons for some parts of the current >> implementation, for example: can someone shed some light about the >> purpose of the (unused) QgsServerLogger class? Why QgsMessageLog >> doesn't work inside the FCGI loop (but works from the command line)? > > QgsMessageLog needs listeners to its signal. This can be QgsMessageLogViewer > (like in desktop) or QgsMessageLogConsole. > > It was changed in a3452a5 - before it didn't use signals (which broke when > threads were used) and would automatically log to the console when no logger > was registered. > > Now you need to explicitly instantiate a QgsMessageLogConsole object and it'll > automatically connect to the signal and log to the console. > > QgsDebugMsg is something else. It's only included in debug builds (using > -DQGISDEBUG), in release builds it's a noop. > >
Hi Juergen, Thank you for the clarification, I've found the problem: there are two different env vars: QGIS_SERVER_LOG_FILE and QGIS_LOG_FILE I probably messed up my configuration: sorry for the noise. -- Alessandro Pasotti w3: www.itopen.it _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
