[Insight-developers] Logging in ITK

[William A. Hoffman]

Why not just turn it on by default?  Why should all the dashboard maintainers have
to muck with stuff?  Turn it on early in the morning, and see how the continuos goes,
and then if it looks bad, turn it off at night so the nightly is not messed up.
That should catch most of it.  

-Bill


At 12:54 PM 3/14/2005, Blezek, Daniel J (Research) wrote:
>Hi all, At last week's tcon I volunteered to add a logging package to ITK.  The proposal is here: http://www.itk.org/Wiki/Proposals:Logging.  I have put log4cxx into the Utilities directory of the Insight checkout, with a rudimentary CMakeLists.txt file.  By default building and test log4cxx are disabled, and must be enabled through the USE_LOG4CXX option (it's marked as advanced).  Would owners of dashboards please enable this flag so I can start debugging the library on multiple platforms?  If possible, could a CMake expert look at my configuration?  I doubt it's very good.
>
>The is a smoke test called log4cxxTest, I'll be checking on this over the next week or so.
>
>Thanks,
>-dan
>
>Daniel Blezek, PhD
>GE Global Research
>Computer Scientist
>
>T 518 387 5481
>F 518 387 6981
>D *833-5481
>E blezek at research.ge.com
>www.research.ge.com
>
>1 Research Circle
>Niskayuna, NY 12309, USA
>
>General Electric Company
>
>_______________________________________________
>Insight-developers mailing list
>Insight-developers at itk.org
>http://www.itk.org/mailman/listinfo/insight-developers