David McNab <david at rebirthing.co.nz> writes:

To answer the "who" question, joliveri made changes with log
messages that indicate a move from a dual-world view to unified code
that should build on Unix and Windows. See the log messages in
<URL:http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/freenet/Contrib/fcptools/ezFCPlib/_fcpGlobals.c>
for example.

> The basis of my outburst is that I put a hell of a lot of time into
> making fcptools work on linux and windows, and to keep the ezFCPtools
> API identical, and the tool command line options.

People are grateful for that.

> This was done with client writers in mind, and was intended to empower
> client authors to create platform-independent clients - either console
> progs, or GUI apps using wxWindows, FLTK, GTK+ etc.
> 
> Prior to fcptools, there was already libfcp, which was *nix-only. The
> only raison d'etre for fcptools was a degree of platform-independence.

>From what I saw, joliveri has the same goal, only the path may be
different than yours. And I have to agree that unified portable code
(if possible!) is easier to maintain then two, three, n
platform-specific versions.

> It feels like my effort was wasted. FreeWeb won't even build with the
> cvs version of ezFCPlib. I was going to re-write FreeWeb to use FLTK,
> and thus build native Windows and Linux versions.
>
> I'm no particular fan of windows, and ultimately plan to make my
> network a 'doze-free zone, but with the blatant and deliberate removal
> of windows platform support, I have lost enthusiasm.

I'm convinced that windows support was not *deliberately* removed. It
may be buggy or outright broken at the moment (coming from CVS, after
all), but that doesn't mean that noone wants it fixed!

Please don't throw in the towel and keep coding for Freenet!

-- 
Robbe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.ng
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20011216/14713f8d/attachment.pgp>

Reply via email to