Re: [Log4cpp-devel] Porting log4cpp to other platforms

[Harald W. <Har...@gm...>]

Thanks for the information about log4cpp project management, if that's
what you call it. Maybe you can just cut'n'paste the corresponding section
from your email into the project homepage or the log4cpp README, then
you won't have to answer this question agian ;-)

The CVS and patch handling is clear and makes sense; the only problem I
see - and again, this question has probably been asked by many sourceforge
contributors before - is how to access the repository across a company
firewall.

We can only do HTTP and FTP over a Squid proxy, and that's it, no SSH and
certainly no cvs pserver on port 2401. Is there some way of tunneling cvs
over HTTP?

Probably not, so I'll either have to coax our sysadmin to open the ssh port
or do my cvs work from home, as a last resort...

Anyway, I'll brush up my results and send in patches for QNX and WinCE,
hopefully some time next week.

Going by your definition, I'm afraid that WinCE doesn't qualify as a
"decent"
platform, but alas, it's what our customers want.... And the core parts of
log4cpp
do work, after some more or less tricky hacks (the biggest problem is
exception
handling, or the lack of it). The question is whether or not you want to see
them
on the log4cpp main trunk.

I'll post more details on the WinCE thread of this list.

Regards,

Harald

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net