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

[Bastiaan B. <Bas...@li...>]

On Wed, 2002-09-04 at 10:14, Harald Wellmann wrote:
> 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 ;-)
> 

Good idea.

> 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 there is, but SourceForge doesn't provide such a tunnel.

> 
> 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...

Getting that ssh port open will be useful for other purposes as well, so
it's worth a try.
Alternatively there is an alternative that should work well enough: at
http://cvs.sourceforge.net/cvstarballs/log4cpp-cvsroot.tar.gz you can
download a tar ball of log4cpp's CVS repository. With that it's trivial
to set up a local CVS repository copy and work with that instead of the
real CVS repository.

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

OK, I'm looking forward to them. Looks like the QNX stuff easily can be
included for 0.3.3 (if you don't mind I go ahead with the 0.3.2 release
later this week). 
For the WinCE stuff we'll have to work out the best way to fit it in (or
not).

> 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'm afraid the restrictions imposed by WinCE would make work on log4cpp
too unpleasant for developers on more 'decent' platforms, but I won't
judge before I see the details. 

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

OK.

Regards,

Bastiaan

> Regards,
> 
> Harald
> 
> -- 
> GMX - Die Kommunikationsplattform im Internet.
> http://www.gmx.net
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Log4cpp-devel mailing list
> Log...@li...
> https://lists.sourceforge.net/lists/listinfo/log4cpp-devel