Re: [Firebird-devel] Questions while porting to WCE

[John B. <bel...@cs...>]

William,
	This is a good example of why you mention your work on the devel 
list before starting.  I have already ported the firebird client (the 
TCP client only) to wce.  It seems like you are trying to port the 
server as well, is that correct?  See additional comments below.

On Wednesday, March 27, 2002, at 06:39 PM, William Baker wrote:

> [...]
> Most of the fixes have been in makefiles, with a few defines and 
> includes
> added directly to the code.  But there are some things in firebird which
> really should be improved, and are easy to do.  These include the 
> following:

I created a new evc project, and that worked for me.

>
> There are two MSG structures, one in jre and the other in remote.
> This name conflicts with a windows structure..not just a wce problem.
> The code uses some dubios #ifdef's and depends on the correct order
> of includes to compile properly.  These hacks won't work on wce,
> and as other versions of Windows headers appear (cygwin,celib,
> openwatcom), it will be close to impossible to ensure #include's don't
> have problems.  Could these be renamed to GDEMSG, REMOTEMSG,
> or something similar?

On the surface the idea sounds reasonable.  But it is possible it is 
more difficult than first appearances.

>
> There is also a name conflict with UNICODE.  typedef USHORT UNICODE;
> is really not correct.  Instead of UNICODE, you really want to use 
> wchar_t.
> I think it's ANSI.
>
> Why are the references to tape drives in the code?  Seems strange.

Beats me.  Probably had the ability to backup/restore to/from tape at 
one point.

>
> In the ipserver directory, not all the networking stuff corresponds to 
> WCE.
> WCE has no drives, no shares, no named pipes, and no groups.  There is 
> no
> easy way to segment the networking code.  This has been the only real
> challenge involving hacking code.  And this is the only area that I am
> really
> not sure exactly how to handle.  It would be nice to have something 
> like:
>
> #define HAVE_WNET
> #define HAVE_TCPIP
> #define HAVE_SPX
> #define HAVE_SHARES
> #define HAVE_NAMED_PIPES
> #define HAVE_...
> #define HAVE_TAPEDRIVE
>
> or something similar.

Sounds like a lot of work to put into FB1 to get the server working on 
wce.  I can understand the usefulness of a functioning server in a 
completely embedded install, but will the client fit your needs?  If 
not, feel free to ask more questions, we are more than willing to help.

> All I really want for now is TCPIP.

A good starting point.

> [...]

-John