Hi everybody! Just wanted to mention that... GNU autotools based build should remain workable.
I have used log4cxx with autotools for 3 years at least. Last year it was added to buildroot project which uses autotools also. http://git.buildroot.net/buildroot/commit/?id=6ebb930b694e97e5cf85a724957d9c0eb129dea7 Buildroot http://buildroot.uclibc.org/ (allows cross compilation of software for many diffferent embedded CPU architectures from linux environment) Notice, trunk tree from old log4cxx repository needed one patch minimun to be able to build... LOG4CXX_385 https://github.com/roland2025/log4cxx this builds on ARM (tested by me) - confirmed working GCC/G++ versions (application running in embedded device, using RollingFileAppender with FixedWindowRollingPolicy. variable work loads, haven't seen crashes caused by log4cxx ) Intel PXA270 GCC4.6.1 Freescale i.MX25 GCC4.5.3 Freescale i.MX53 GCC4.5.3 Freescale i.MX51 GCC 4.? http://www.artila.com/en/p_som.html M501(Atmel 9200) GCC3.3.4 M502(Atmel 9G20) GCC4.6.1 I've only had trouble on PC with extra high logging load (TRACE) when some apr library crashes while using socketappender. Best regards, Roland Uuesoo On Fri, Jan 3, 2014 at 4:26 PM, Rhys Ulerich <[email protected]> wrote: > > I tend to believe that we should start to build log4cxx with Ant. My > feeling is that > > Maven was using Ant to build it. If the Ant stuff works, we could > renenable the Maven build for it, > > or leave it out. > > Ah, sorry for crying wolf. I had hit a classpath issue with the cpptasks > JAR. I didn't recognize it at first from the stacktrace. > > With those lines enabled in the pom.xml I can get somewhere. Christian is > the pom used in some automated fashion by Apache Infra jobs? Do I need to > worry about breaking a cronjob if I remove the comments around those > plugins? > > - Rhys >
