<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Normally I would expect software to be updated if it doesn't compile properly with new gcc versions. At least in my case (gcc 4.4.3) it required a little patching. I know it is easy to fix but it does give a signal of not being maintained.</div>
</blockquote><div><br></div><div>The compilation issues appear to be fixed in their svn trunk (for a couple years now). I agree it's annoying they haven't done a release.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
I understand your argument about using a library with available packages for the different platforms, and that boost log has some drawbacks here. I am very interested in hearing about other possibilities.</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
My focus is more on cross compiling since I will be using ROS in commercial robot products. And I don't expect ROS to be build natively in these products. And in this case I found that log4cxx adds some unnecessary complexity, for adding such a "general" thing as logging.<br>
</blockquote><div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8">This isn't a dependency that can change any time soon, due to backwards compatibility and other packages using log4cxx to hook into ROS logging. We're happy to accept patches that conditionally provide a different backend for rosconsole as long as it supports the rest of what rosconsole requires. Being able to remove logging entirely, or push it directly to printf is another option.</div>
<div><br></div><div>Really though I'd recommend just using it -- it isn't that difficult to get cross-compiling, and any other option (other than removing use of a 3rdparty dependency entirely) is likely to cause its own headaches.</div>
<div><br></div><div>Josh</div></div>